5 Replies Latest reply: Jul 29, 2006 1:46 PM by Glen Avery RSS

GRA_PROCESS_MONITOR 1.8.3

Glen Avery

GRA_PROCESS_MONITOR


Version History
====================
v1.8.3 031208 Tom/Corrected agent config cleanup apon instance deletion
v1.8.2 031111 Corrected cluster logic when using filesystem flag. Corrected config file flag logic
when file does not exist
v1.8.1 030929 Correct poll delay/timeouts function
v1.8.0 030916 Added poll delay/timeouts function
v1.7.3 030807 Corrected ExtraFilesList parameter
v1.7.2 030715 Added ExtraFilesList parameter containing GRA_PROCESS_MONITOR.kml
v1.7.1 030518 Rewrote min/max threshold code
v1.6.0 030428 Added functionality to set min and max thresholds to 0 so that an alarm will be raised when
a process exists
v1.5.0 030403 Added 'Exclude Child' functionality
v1.4.3 030126 Minor changes to GUI
v1.4.2 030126 Corrected a problem with downtimes
v1.4.0 021118 Renamed PROCESS_MONITOR to GRA_PROCESS_MONITOR
v1.3.8 020829 Corrected a bug with child process monitoring and added CPUCpuUtil (%) parameter to
PROCESS_MONITOR_PROC
v1.3.6 020807 Corrected a bug with downtimes
v1.3.5 020625 Corrected some bugs, including a problem with PROCESS_MONITOR_SPY on Solaris.
v1.3.0 020613 Improved GUI and add config file/filter functionality
v1.2.7 020305 Minor improvements
v1.2.0 010920 Added the PROCESS_MONITOR_SPY class for monitoring cpu and memory statiscs of all
processes according to a filter (include/exclude username/wildcard)
v1.1.8 010917 Fixed some minor errors. Added support for automatically monitoring child processes
v1.1.7 010814 First version released to DEVCON


Platforms
==========
This KM has been tested on the following
1) Compaq Tru64 v4 and v5
2) Solaris
3) HPUX
4) Windows (NT & 2000)


Introduction
=============

This KM can monitor processes.

Here is a description of the menu commands for the PROCESS_MONITOR application class
1) KM Admin->Group->Add : Adds a process group. Used for group processes which belong to the same application
2) KM Admin->Group->Remove : Removes a process group
3) KM Admin->Add : Adds a process to a process group.
4) Set Cluster : If this set to a service or filesystem name then the monitoring will only be active if these are present on the local machine
5) Set Downtime : If a process group has regular scheduled downtime then this can be set so that no false alarm is raised.

Here is a description of the menu commands for the PROCESS_MONITOR_PROC application class
1) Set Threshold : Used for setting the minimum and maximum number of processes allowed before an alarm is raised
2) Set Alarm Time Delay : It is possible to set a delay so that if the process is down for less than this time than no alarm will be raised
3) Stop Monitoring
4) Set Recovery Script : Used to set a list of commands to be executed when a process alarms. For example for sending email or running restart scripts.
5) Set Config File : A file and a wildcard can be specified. If this is done then the monitoring will only be activated if the specified file contains the wildcard. This can be used for checking a certain line in a system config file.

If there are any questions/problems please email me on glen_r_avery@hotmail.com

Regards
Glen Avery

  • 1. Re: GRA_PROCESS_MONITOR 1.8.3
    craigt

    Hi Glenn,

    Ive used this previously in large sites running Solaris.

    And in the notes it says tested on Windows.
    I've tried it on Win2k & Win2003.

    any process being monitored will show up in the "list processes" km command. Proc Count populates incorrectly, and all other metrics (mem/cpu etc) are 0.

    watching patrol agent: list processes output is:
    Parent Processes
    ================

    3404 572 SYSTEM ? 0 3329 PatrolAgent PatrolAgent


    Child Processes
    ===============

    I've set /GRA_PROCESS_MONITOR/debug, but havent seen any output to the SOW.

    Is this KM meant to work for monitoring windows processes? or just run on windows consoles?

    Cheers
    Craig

  • 2. Re: GRA_PROCESS_MONITOR 1.8.3
    Glen Avery

    I have never seen the problem you mention on Windows. Could you send me a copy of your agent config as well as the version of Windows and the Patrol Agent you are using?

    Is the PSL function process() returning correct values?

    Try this in a command window

    %PSL print(process());

    Debug output should be written to the SOW every time the PROCnumberProcs parameter is updated.

    Thanks
    Glen

  • 3. RE: GRA_PROCESS_MONITOR 1.8.3
    kaeser

    Hi Glen,

    will it be possible in future to raise alarms, if a special amount of used memory has exceeded?
    Also we are looking for a solution being able to monitor handles like shown in the Windows task manager and the possibility to raise an alarm if a treshold has exceeded.
    Do you see any chance that your process km will contain these features in the future?

    best rgds.
    Jürgen

  • 4. RE: GRA_PROCESS_MONITOR 1.8.3
    2009-001

    I've found some things in the code which can be improved:
    The Menu Kommand sets the Values for Include Children to 1 (ignore), 2 (include), 3 (Exclude), but the km works with 0, 1, 2
    Additionally you use on unix the default ps command for the processes, but the PSL process() for the children. This can lead to false results because of timing problems.
    And on solaris the options shown in the default ps command are cut after a limited number of characters.
    Better use /usr/ucb/ps auxwww to see the full command line, especially for java processe.
    But still, good work.

  • 5. RE: GRA_PROCESS_MONITOR 1.8.3
    Glen Avery

    Hi!

    Thanks for the input and praise.

    If you would like to email me a improved version of the KM with appropriate comments for the version history then I will see that it gets uploaded here.

    Cheers and Thanks
    Glen