Use this Knowledge Script to monitor services on remote computers. You specify the computers and services to monitor. A service that is detected as down can be restarted. The Windows services include those that are not discovered by AppManager, such as WinLogon or NetIQ Corporationms.
Before running this script, run the ConfigRemoteServiceDown Knowledge Script to store a list of computers and services in the local repository on the target computer.
After you run ConfigRemoteServiceDown on each target computer in a group, you can use RemoteServiceDownLR in a monitoring policy for the group. On each computer, RemoteServiceDownLR knows what to monitor because ConfigRemoteServiceDown has stored that information in the local repository.
This script displays event information even if the remote computer is in maintenance mode.
NOTE:The AppManager agent does not need to be installed on the remote computer you want to monitor, nor does the remote computer need to exist in the Navigation pane or the TreeView pane.
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 service is down? |
Set to y to raise an event if a service is 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 service status. The default is n. |
|
Collect data only on service down? |
Set to y to collect data only when a service is down. If enabled, and if the Collect data? parameter is also enabled, this script returns a value of 0 to indicate that a service is down. 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 failed. 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 succeeded. 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 you have selected not to restart it. The default is 18 (yellow event indicator). |
|
Event severity for service not found |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which a selected service cannot be found. The default is 8 (red event indicator). |