AppManager provides preferences for you to specify how you want your jobs to collect data. You can set these preferences for individual jobs by clicking the Advanced tab in the Knowledge Script Properties dialog box. You can set preferences for collecting detail data, the schedule for collecting data, and collecting data in response to an event.
By default, every time you run a Knowledge Script and collect data, AppManager returns a data point value (for example, 50) but does not return a detailed description (for example, CPU utilization is 50%). In general, when you view the data in charts, graphs, and reports, you usually focus on the value and not the details. However, in some cases, you might want additional information. For example, the NT_TopCpuProcs Knowledge Script can include a list of the processes consuming the most CPU in its detail message, but you must enable it to include the additional information.
To reduce the amount of space the data in your repository takes up, use the options available on the Advanced tab of the Knowledge Script Job Properties window to configure AppManager to collect data details differently for individual jobs. To collect the value of the monitored resource and detailed information, such as server name and collection time, enable the Collect data details with data point preference.
To change the default behavior for data collection for all jobs, use the Operator Console.
NOTE:Changing the default behavior for data collection in the Operator Console does not affect default settings for the Control Center console.
To change the default behavior for collecting data details:
Select File > Preferences in the Operator Console.
Click the Repository tab, and then click Advanced Properties in the Knowledge Script options group.
To collect the value of the monitored resource and detailed information, such as server name and collection time, select Collect data details with data point.
This option only applies to data collection for AppManager graphs and charts.
Click OK to save the changes.
When you run a Knowledge Script and collect data, AppManager returns a data point value for every job iteration, storing each data point in the repository--requiring more data space and more database management.
In some cases, collecting a data point at every job iteration might not provide useful information. If you want to run a Knowledge Script on a frequent basis (for example, every 5 minutes) but don’t need to collect and store a data point for each iteration, you can set the Collect data every N job iterations and Calculate average preferences to reduce overhead and, in some cases, more accurately reflect real system performance.
Instead of collecting 12 data points per hour (while the Knowledge Script is running every five minutes), AppManager collects a data point every n iterations and stores fewer data points in your database. Each data point is an average of all the values AppManager collects in each of the n iterations. Averaging the values over several iterations provides a more accurate reflection of system performance.
You can set these preferences on the Advanced tab in the Knowledge Script Properties dialog box for individual jobs, or you can use the Operator Console to set repository preferences that control the default behavior for all jobs.
NOTE:Changing the default behavior for data collection in the Operator Console does not affect default settings for the Control Center console.
To change the default behavior for collecting and averaging data:
Select File > Preferences in the Operator Console.
Click the Repository tab, and then click Advanced Properties in the Knowledge Script options group.
In the Data options group, set the number of times a job should run before collecting a data point in the Collect data every N job iterations preference.
Select Calculate average.
Click OK to save the changes.
Each time you run a Knowledge Script and collect data, AppManager returns a data point. However, if you are more interested in getting information to diagnose a problem and not for charting, graphing, and reporting, you can set repository preferences to collect data in association with event conditions. Using these preferences, you can collect data when the server, application, or process you are monitoring crosses the threshold you specify and raises an event.
For example, you can run the NT_TopCpuProcs Knowledge Script to raise an event if CPU usage on a computer exceeds a 90% threshold. Set this job to Start collecting data when an event is generated because when CPU utilization reaches 90%, you want to know what processes are responsible and create a report that lists the causes of the high CPU. AppManager only creates a data point when the threshold you specify (in this case, 90%) is exceeded. This prevents your database from filling up with information you might never use.
You can then use the Stop collecting data when event condition no longer exists preference to stop data collection after you fix the problem that generated the event.
You can set these preferences on the Advanced tab in the Knowledge Script Properties dialog box for individual jobs, or you can change the default behavior by setting the Advanced Properties repository preferences.
NOTE:Changing the default behavior for data collection in the Operator Console does not affect default settings for the Control Center console.
To change the default behavior for collecting data only when an event condition exists:
Select File > Preferences in the Operator Console.
Click the Repository tab, and then click Advanced Properties in the Knowledge Script options group.
In the Data options group, select Start collecting data when an event is generated.
(Conditional) If you want jobs to stop collecting data when the event condition no longer exists, select Stop collecting data when event condition no longer exists.
Click OK to save the changes.