How to monitor a process with a long name using IBM Tivoli Monitoring OS Agent
AntonioSgro 120000718K Visits (8472)
Before IBM tivoli Monitoring 6.2.2 FP03, the max length for a process name to be monitored using ITM OS Agent on Unix was limited to 768 characters; it didn't allow to monitor processes like Java that have a command line longer than 768 characters; with the above limitation, critical processes like WebSphere processes were not monitored and users were not alerted if the process was running or not.
Starting from ITM 6.2.2 FP03, a new attribute has been introduced in order to allow to monitor the availability of processes with a name longer than 768 characters.
The new attribute is ProcessFilter and allows to use regular expressions to monitor long process names.
Here is an example about how it works:
Let's suppose to have two processes with the following name:
java -Dheapsize=768 myarg1 myarg2 myarg3 ...... myargn com.
java -Dheapsize=512 myarg1 myarg2 myarg3 ...... myargn com.
If a user wants to monitor the first process and be alerted if it consumes more than 80% cpu, it can use now the following rule:
In brief, what will happen is that the agent will match the processes names with the ProcessFilter rule and will fill the ProcessCommand attribute with the info within brackets so Process Command attribute will be equals to java AppServer1