Summary:
How to configure CA SystemEDGE to monitor processes based on parameters received on execution line.
Background:
Certain application call the same process (binary) with different parameters to instruct it to provide different functionalities or services. As an example, many applications use java process as main process and service provided depends on the configuration file passed as parameter on command line that start it.
On this circumstances monitor the existence of main process could not help as many instances of it could be running, to distinguish it CA SystemEdge also allow to monitor the parameters used when process instance was started.
Environment:
All environments
Instructions:
1) Stop CA SystemEdge Agent
2) Modify the sysedge.cf to configure the file system watchers.
Sysedge.cf is in the CA SystemEDGE data_directory,
The default path in unix,
/opt/CA/SystemEDGE/config/port1691/sysedge.cf
The default path in windows,
C:\Users\Public\CA\SystemEDGE\port1691\sysedge.cf
3) Add your LogFile watcher to the sysedge.cf as this way:
watch process <attr> '<regexpr>' <index> <flags> <interval> <stype> <oper> <thresh> ['<descr>' ['<action>' ['<objClass>' '<objInst>' '<objAttr>' <severity>]]]
Example:
On next example we’ll check if it is running a process that contains in sequence at execution command line the “notepad” and “CAweb.cf” strings.
watch process procAlive 'notepad.*CAweb.cf' 13 0x800 30 absolute = 4 'CA Web Services' '' 'Process' '' 'Alive' Ok
4) Restart the CA SystemEDGE Agent
On windows you can restart the agent in the services.msc
On Unix you can go to run the following command:
/opt/CA/SystemEDGE/bin/sysedgectl restart
Additional Information:
KB000038277 How to configure CA SystemEDGE to monitor and evaluate amount of files on a specific path
KB000029809 CA SystemEDGE Monitoring Windows Performance Counters
KB000035359 Can CA-SystemEDGE monitor Custom Windows event logs?