|
|
Use config Rollup to define how long, in days, different types of report data is stored in the SQL report database before it is automatically deleted by the Rollup and Aging daemon "dbrolld". This chapter describes how to edit aging parameters to suit your reporting and database administration needs.
The aging parameters you define determine the minimum utilization percentage required to log information to the database, and the number of days protocol, segment, host, and conversation information stays in the detail and summary database tables. By specifying a minimum utilization percentage parameter, you define what level of protocol usage must reach or exceed for information to be logged to host and conversation databases. In this way you can define the utilization percentages that are significant to you.
You can specify the number of days you want to keep detail and summary data for each statistic type--protocol, summary, host, and conversation-- before it is automatically deleted by the dbrolld daemon. For example, you may want to keep daily or monthly summary data to use for long term trend monitoring; to do this you would specify 365 days for summary aging. On the other hand, you may only want to keep detail data for several days and delete it on a weekly basis; to do this, you would specify seven days for detail aging.
To customize these parameters for each statistic type perform the following steps:
Step 1 Launch TrafficDirector from the Admin level of the TrafficDirector main window, if you have not already done so.
Step 2 Click the Config Rollup icon.
The Configure Rollup window is displayed (Figure 46-1). Note that all fields are set to the TrafficDirector default values.
Step 3 Enter the number of days for detail aging for each database table. You can specify one or more days for the Protocol, Segment, Host, and Conversation table.
Step 4 Enter the number of days for summary aging for each database table. You can specify one or more days for the Protocol, Segment, Host, and Conversation table.
Step 5 Enter the minimum utilization value that must be reached or exceeded to log host or conversation information.
Step 6 Click Apply to save and apply the aging parameters, or click Cancel to cancel and reset all fields.
TrafficDirector uses the following daemons to collect raw data from your network probes, process it into usable data for reporting, and sort it into tables in the SQL report database:
| Snapshot daemon | Retrieves snapshots of raw statistics from agents and stores them in a snapshot table. The type of information the collected and the rate are determined by logging parameters that you configure in the agent. |
| Extraction daemon | Retrieves information from the snapshot table and uses it to create rows in the details table. |
| Rollup & Aging daemon | Gets information from the details table to create new rows in the summary table. This daemon also deletes or "ages out" obsolete information from the detail and summary tables at intervals that you define using Config Rollup. |
|
|
