3.19 Host_ProcessDown

Use this Knowledge Script to access the Host Resource MIB to determine whether specified processes are not running. This script raises an event if a specified process is not running. In addition, this script generates datastreams for process status.

3.19.1 Resource Object

NetworkDevice Host Processor Folder

3.19.2 Default Schedule

By default, this script runs every 5 minutes.

3.19.3 Setting Parameter Values

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_ProcessDown 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 not running?	Select Yes to raise an event if a specified process is not 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 (comma-separated)	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.
Enable cache PID mechanism for better performance?	Select Yes to cache the PIDs for the processes specified in the Processes to monitor parameter. When enabled, the PIDs are cached and it optimizes the performance of the job. The default is No.
Collect data for process status?	Select Yes to collect data for charts and reports on status of process. If you enable this parameter, data collection returns a value of 100 when a specified process is running, or a value of 0 when the process is not running. Selecting this parameter collects data for all the processes that are being monitored. The default is unselected.
Collect data for the processes specified in the list?	Select Yes to collect data for chart and reports for specific processes. Selecting this parameter collect data only for specific processes specified in the Specify the list of processes for data collection parameter.
Specify the list of processes for data collection	Specify one or more process names, separated by commas and no spaces for which you want to collect data. You must specify at least one process if you selected the Collect data for the processes specified in the list? parameter. For example, if you are monitoring proc1, proc2, and proc3 but has not specified any process for this parameter, then the data will be collected for all the processes that are being monitored. Also, events will be generated if any of these processes are down. On the other hand, if you are monitoring proc1, proc2, and proc3 and specify the data collection for proc3, proc4, and proc5, then event will be generated for proc1, proc2 and proc3 if any of these processes are down. But, data will be collected only for proc3, proc4, and proc5. NOTE:The process name that you specify should match the process name running on a device.
Event severity when process is not running	Set the severity level, from 1 to 40, to indicate the importance of an event in which specified processes are not 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 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.