Use this Knowledge Script to access the Host Resource MIB to verify whether a specified process is running. This script raises an event if a specified process is running and generates datastreams for process status.
NetworkDevice Host Processor Folder
By default, this script runs every 5 minutes.
Set the following parameters as needed.
Parameter |
How to Set It |
---|---|
General Settings |
|
Job Failure Notification |
|
Event severity when job fails |
Set the event severity level, from 1 to 40, to indicate the importance of the failure of the Host_ProcessUp job. The default is 5. |
Event severity when job returns warnings |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the job completes with warnings. The default is 25. |
Event severity when monitoring fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event that is raised when monitoring fails. The default is 25. |
SNMP Settings |
|
SNMP timeout |
Specify the length of time in milliseconds that the job should wait for the SNMP response from the monitored network device before timing out and raising a failure event. The default is 2000 milliseconds. |
SNMP retries |
Specify the number of times the job should attempt to get the SNMP response from the monitored network device. The default is 1 attempt. |
Enable use of SNMP GETBulk operations? |
Select Yes to enable SNMP GETBulk operations. GETBulk operation requests a number of GETNEXT responses to be returned in a single packet than issuing multiple GETNEXT operations. The GETBulk operation uses less bandwidth and optimizes the agent in retrieving the data from MIB instrumentation. The default is unselected. |
Number of row to request for each GETBulk operation |
Specify the number of rows that should be retrieved for each GETBulk operation. You can specify a maximum of 200 rows. The default is 10. |
Raise event if process is running? |
Select Yes to raise an event if a specified process is running. The default is Yes. |
Collect data for process status? |
Select Yes to collect data for charts and reports. If enabled, data collection returns a value of 100 when a specified process is running, or a value of 0 when the process is not running. The default is No. |
Processes to monitor |
Specify one or more process names, separated by commas and no spaces. For example: grep.exe,batch.exe NOTE:If the device being monitored is running on Microsoft Windows, the process name specified should match the Image Name seen on the Process tab in Task Manager. |
Event severity when process is running |
Set the severity level, from 1 to 40, to indicate the importance of an event in which the specified processes are running. The default is 10. |
Raise one-time events? |
Select Yes to raise an event for all one-time events. If you set this parameter to Yes, then AppManager raises an event when a particular performance counter cannot be found in an iteration. For example, if this script does not find a particular performance counter in the first iteration, AppManager raises an event on the first iteration and does not raise further events for consecutive failures. This script raises further one-time events only on the iteration when there are failure events following successful retrieval of the performance counters. If you do not want to see such one-time events, set this parameter to No. |