Use this Knowledge Script to determine whether specified processes are currently running. AppManager raises an event if a specified process is not running or if the minimum number of processes are not running.
UNIX CPU folder
The default interval for this script is Every 5 minutes.
Set the following parameters as needed:
Description |
How to Set It |
---|---|
Raise an event if the process is not running? (y/n) |
Set to y to raise events. The default is y. |
Collect data for processes not running? (y/n) |
Set to y to collect data for charts and reports. If set to y, the script returns data for each named process. A value of 100 is returned if the process is running; a value of 0 is returned if the process is not running. The default is n. |
Processes to monitor (comma-separated) |
Enter one or more process names, separated by commas and no spaces. For example: grep,batch |
Minimum number of each process required (comma-separated) |
Enter the minimum number of instances that have to go down before you want AppManager to raise an event. If you are monitoring more than one process, list the numbers for each process separated by commas and no spaces. The default is 1. For example, if you do not want to raise an event every time the grep and batch processes goes down, but you do want to raise an event after 10 instances of the process go down, enter: 10,10 |
Event severity when process is down |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 8. |
Event severity for internal failure |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which this job experienced an internal error. The default is 5. |
Enable debugging? (y/n) |
Set to y to enable debugging. The default is n. |