Use this Knowledge Script to monitor any pair of System Monitor performance counters. You can run this script on any computer or server, and you can monitor any counters available in the System Monitor. You can observe either a maximum or minimum threshold for each counter you are monitoring. You can set the script to raise an event if the value of either counter exceeds or falls below the threshold you set.
To see a list of available counters, click Browse [...] in the Name of counter to monitor parameter or start the System Monitor and click Add [+] in the toolbar.
Use this Knowledge Script to monitor for conditions when the values for any pair of counters indicate a problem. For example, you can raise events when CPU and memory counters both exceed a high threshold, or when a data file size counter exceeds a high threshold and an available disk space counter falls below a low threshold.
Requirements for Windows Server 2012, Windows 8, Windows 7, Windows 2008 R2, and Windows 2008:
The Log On As account under which the AppManager agent runs for these Windows operating systems must be a domain account and belong to the Administrator local group.
Requirements for Windows Server 2003:
The Log On As account under which the AppManager agent runs on Windows Server 2003 must belong to the Performance Monitor Users policy.
If the Operator Console or Control Center is installed on Windows Server 2003, the user account under which the console application runs must belong to the Performance Monitor Users policy.
To check the local policy:
At a Command Prompt, type gpedit.msc and press Enter.
In the Group Policy snap-in, double-click Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.
In the Local Setting column, ensure the appropriate user account belongs to the Performance Monitor Users policy.
If the Operator Console or Control Center is installed on Windows Server 2003, the Remote Registry service on the console computer must be running. If the Remote Registry service is down when you attempt to configure this script by browsing counter information on the remote computer, the console displays an error message that indicates AppManager was unable to connect to the remote computer.
Requirements for Windows Vista:
If the Operator Console or Control Center is installed on Windows Vista, the Remote Registry service on the console computer must be running. If the Remote Registry service is down when you attempt to configure this script by browsing counter information on the remote computer, the console becomes unresponsive.
Windows computer or application server, such as Exchange Server, SQL Server, IIS server
The default interval for this script is Every 5 minutes.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Collect data for counter value? |
Select yes to collect data for charts and reports. If enabled, data collection returns values for counters that exceed the threshold. The default is n. |
|
Raise event if counter value exceeds or falls below threshold? |
Select yes to raise an event when a counter value counter exceeds or falls below the threshold you set. The default is yes. |
|
Counter 1 Settings |
|
|
Counter value for threshold |
Specify the value for the threshold you want to observe. The default is 600. |
|
Use counter value as maximum threshold? |
Select yes to use the value from the Counter value for threshold parameter as a maximum threshold. The script then raises events when the counter value exceeds the threshold. Deselect the yes to use the value from the Counter value for threshold parameter as a minimum threshold. The script then raises events when the counter value falls below the threshold. The default is yes. |
|
Name of counter to monitor |
Specify the object\counter\instance name or click Browse [...] to select the object, counter, and instances to monitor. If typing the name, use the format <object>\<counter>\<instance>. You can enter multiple instances, separated by commas. For example: Process\% Privileged Time\mapisp32,mqsvc If an instance is a parent of multiple instances (for example, if you have a Logical Disk 0 with partitions C: and D:), enter the complete instance name exactly as displayed in Performance Monitor (for example “0 ==> C:”). For more information, see Examples of Using This Script. |
|
Counter 2 Settings |
|
|
Counter value for threshold |
Specify the value for the threshold you want to observe. The default is 600. |
|
Use counter value as maximum threshold? |
Select yes to use the value from the Counter value for threshold parameter as a maximum threshold. The script then raises events when the counter value exceeds the threshold. Deselect the yes to use the value from the Counter value for threshold parameter as a minimum threshold. The script then raises events when the counter value falls below the threshold. The default is yes. |
|
Name of counter to monitor |
Specify the object\counter\instance name or click Browse [...] to select the object, counter, and instances to monitor. If typing the name, use the format <object>\<counter>\<instance>. You can enter multiple instances, separated by commas. For example: Process\% Privileged Time\mapisp32,mqsvc If an instance is a parent of multiple instances (for example, if you have a Logical Disk 0 with partitions C: and D:), enter the complete instance name exactly as displayed in the Performance Monitor (for example “0 ==> C:”). See System Monitor for the exact spelling of counter names and details about what each counter represents. |
|
Event severity when counter value exceeds or falls below threshold |
Set the severity level, from 1 to 40, to indicate the importance of an event if a counter value exceeds or falls below the threshold you set. The default is 8 (red event indicator). |