4.16 IntervalCounter

Use this Knowledge Script to monitor changes in any performance monitor counter. You can specify a consecutive number of times that the Counter delta value threshold parameter must be exceeded before the script raises an event. This script automatically raises an event if it does not find the counter to monitor.

This script collects the counter value delta between script executions for the object\counter\instance you are monitoring. A negative counter value delta indicates that the counter value has decreased.

4.16.1 Prerequisites

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:

    1. At a Command Prompt, type gpedit.msc and press Enter.

    2. In the Group Policy snap-in, double-click Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.

    3. 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.

4.16.2 Resource Objects

Any discovered Windows computer or application server, such as Exchange Server, SQL Server, or Proxy Server

4.16.3 Default Schedule

The default schedule for this script is Every 5 minutes.

4.16.4 Setting Parameter Values

Set the following parameters as needed:

Description

How to Set It

Collect data?

Set to y to collect data for charts and reports. When enabled, data collection returns the counter value delta between script executions for the object, counter, or instance you are monitoring. The default is n.

Event when over threshold?

Set to y to raise an event if the counter value exceeds the threshold. The default is y.

Counter delta value threshold

Specify the maximum allowed value for the difference between the counter value from the previous job iteration and the current job iteration. The default is 600.

Counter to monitor

Enter the object, counter, or instance name, or click Browse [...] to select the object, counter, and instances to monitor. The default is Objects\Threads\.

NOTE:You can also start the System Monitor and click Add [+] in the toolbar.

Use the format: <object>\<counter>\<instance>\. You can enter multiple instances, separated by commas. For example: Process\% Privileged Time\mapisp32,mqsvc. If the counter does not have an instance name, end the string with a backslash: Process\% Privileged Time\.

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:").

Consecutive times

Specify the maximum number of consecutive times the counter must exceed the threshold before this script raises an event. The default is 1.

Event severity level - Over threshold

Set the event severity level, from 1 to 40 to indicate the importance of an event in which the counter value exceeds threshold. The default is 8 (red event indicator).

Event severity level...

Set the event severity level, from 1 to 40 to indicate the importance of an event in which the monitored counter or instance cannot be found. The default is 15 (yellow event indicator).