Use this Knowledge Script to detect whether specified services on the computer on which you run the script are down. A service detected as down can be restarted.The Windows services include those that are not discovered by AppManager, such as WinLogon or NetIQms.
This script requires that you first use the ConfigServiceDown Knowledge Script to store a list of services in the local repository on the computer where ServiceDownLR runs.
Once you have run ConfigServiceDown on each computer in a group, you can use ServiceDownLR in a monitoring policy for the group. On each computer, ServiceDownLR knows what to monitor because ConfigServiceDown previously stored that information in the local repository.
Windows 2003 Server or later
The default schedule for this script is Every 5 minutes.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Raise event if any service is down? |
Set to y to raise an event if services are down. The default is y. |
|
Collect data for service status? |
Set to y to collect data for charts and reports. If enabled, data collection returns a separate datastream for each service you monitor:
The data detail message includes the name of the service, the start type, and the status. The default is n. |
|
Collect data only on service down? |
Set to y to collect data only when a service is down. If set to y, returns a value of 0. Enable this parameter only if the Collect data? parameter is enabled. The default is n. |
|
Auto-start service? |
Set to y to automatically restart down services. The default is y. |
|
Event severity when service down; auto-start failed |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a service is down and auto-start fails. The default is 5 (red event indicator). |
|
Event severity when service down; auto-start succeeded |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a service is down and auto-start succeeds. The default is 25 (blue event indicator). |
|
Event severity when service down; auto-start disabled |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a service is down and the Auto-start service? parameter is set to n. The default is 18 (yellow event indicator). |
|
Event severity when service not found |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a specified service is not found. The default is 8 (red event indicator). |
|
Event severity when Knowledge Script error occurs |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the ServiceDownLR job fails unexpectedly. The default is 35 (magenta event indicator). |