processes
Process monitoring probe

The process watcher probe monitors processes and windows owned by the processes to detect the error situations.


This component requires Nimsoft Robot 3.00 or newer.

Notes


  • Since version 2.40, it is possible to try and retrieve the process information again, if the probe believes the data to be corrupt. This limit has been defined to a default value of 1 (which means: Try 1 more time and then give up). It can be tweaked in the raw-configure to any number between 0 and 10.
  • The probe is unable to get the command line of 64-bit processes on Windows and of all processes on Windows Vista and Windows 2008.
  • Important information about probes running on Windows Vista, 2008 Server and Windows 7:
    Due to the change in Windows that causes services and applications to run in different sessions (previously all of these ran in session 0), probes will not be able to execute those external applications which use GUIs on these platforms.
Revision history
Date Description State Version
06.03.2024

What's New:

  • Added support for creating discovery profiles. These profiles automatically generate monitoring profiles based on the provided information.
    Note: For more information, see Automatically Create Monitoring Profiles with Discovery Profiles using AC or using IM .
  • Added support for configuring alarms for the maximum number of process instances on the server.
  • Added support for stabilization delay, allowing users to delay the execution of monitoring profiles based on the server's uptime.
  • Added support for different clear alarms for each alarm, providing users with more flexibility in managing alarms.

Fixed defects:

  • Resolved an issue where the processes probe failed to display process information for certain processes in the status tab on Windows OS, resulting in inaccurate memory metric data. (Support case 33471066)
  • Resolved an issue in the IM GUI where users could create multiple alarm messages with the same message ID. The probes now restrict the creation to only one instance. (Support Case 33545580)
  • Resolved an issue in the IM GUI where the test connection caused the probe to crash when the name+command line field exceeded 1000 bytes. Probes now prompt users with an appropriate message when the input exceeds 1000 bytes. (Support case 33471066)
SHA-256 Checksum: efd551a0dc20ab32a80edc05c913662df3d3f409c9097de7eaeeb6be11c8c3bb 		GA 4.84
28.09.2023

What's New:
Added the support to monitor the processes on Windows servers that have protection enabled.

Fixed Defects:
Fixed an issue where the binary path of the process was not displayed in the alarms generated by the probe.
Support case 33206044

SHA-256 Checksum: 8759be83839f7bf1135f7ec7eb604fd3b5ea985385b3c65e08fa6e5ca87eaec3 		4.83
01.11.2022

What's New:
Alarm Generation
If any process instance goes down, an alarm is generated when the following are true:

  • The Track Process by Process Identifier checkbox is enabled in the Processes profile through MCS UI.
  • Multiple instances are running.

For example, if the CMD process has multiple instances running and if any instance of CMD goes down, an alarm will be generated with an alarm message as, “Process Availability on CMD [1] for the robot’s name is at 0.00 Running”.

Clear Alarm

  • The alarms are cleared automatically when any instance of the process comes up again, and if no monitored process is running, a profile-level alarm is generated.

For example, “Process Availability on the <profile’s name> for the robot’s name is at 0.00 Running”.

Fixed Defects:
Alerts generated by Alarm policies are not automatically cleared when the process starts again with the "Track Process by Process Identifier" option enabled.
Support case 33082560

SHA-256 Checksum: 6a000c9d5e591797b72d0b2ec5f5ac5aa14c1f708b1ab805fae4eb36f6793783 		4.82
09.09.2021

What's New:

  • Added the ability to clear all the alerts on restart of the probe which are in the un-cleared state before the restart of the probe.
  • The Clear Alarms on restart feature can enabled/disabled from both IM and Admin Console GUI.
  • This functionality is not supported from MCS (using the Operator Console).

Fixed Defects:

  • Processes probe is facing "communication error 80040402". Support Case: 32369228
  • Processes probe abruptly gets deactivated. Support Case: 32649026
  • Frequent alarms, unable to communicate with Processes probe, and restarting the probe. Support Case: 31784899
  • Processes probe displays QOS data for IO Other Data Transfer Rate and IO disk read/write metrics as '0'. Support Case: 31867609
  • Linux server Processes probe, QOS not showing data for IO Other Data Transfer Rate and IO disk read/write metrics. Support Case: 32086388
  • Many alarms are created and closed almost simultaneously in the Processes probe. Support Case: 32202424
SHA-256 Checksum: 16bfce7f3f3d115176bb4a5addf0d3e349c2816414cb991701d365940f13fa81 		4.80
03.03.2020

What's New:

  • Stabilization of the processes probe for Memory consumption and CPU Usage.
  • VS2017 redist package version upgraded to 1.01 from 1.00 as 1.00 was having reboot issue.

Note: Users may see some CPU spike while opening the IM processes GUI or while refreshing the processes list in GUI. This CPU spike will go down, once the GUI operation gets closed.

Fixed Defects:

  • Processes Probe - 4.64 CPU leak on CentOS 6.10 and Ubuntu 14. Support case number 20020534
  • Deployed processes probe version 4.64 to AIX systems and caused issues. Support case number 20024732
  • Processes probe error: Internal error: Unable to find any processes. Support case number 20049414
  • Process probe on AIX 7.1 consuming high cpu. Support case number 01372650
  • Processes probe memory and CPU usage is increasing. Support case number 01301068
  • Problems with the probe processes. Support case number 01344072
  • Processes probe creating cpu spikes of around 5% when polling on zlinux. Support case number 20101877
  • Linux processes probe - memory leak. Support case number 01332245
  • UIM processes probe dependency is for vs2017_vcredist_x version 1.00. Support case number 20092103
MD5 Checksum: 0b251f302e7fae6d39a7cb69c6e25b46
SHA-1 Checksum: c826706b8b92fc6740427796548e26e6949d9d6f 		4.70
31.01.2019

What's New:

  • Added support to monitor metrics on per process basis to determine the process that causes heavy I/O.
  • Added support to monitor the number of files open for processes that impacts the Unix and Linux servers performance.

For Detailed Release Notes-Please refer

https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN

Note: Support case(s) may not be viewable to all

MD5 Checksum: 7bbd3d832ff044368f6215408f306365
SHA-1 Checksum: 584bd40bb51ad3b6fce9e8c7e0b7a7f163ecf302 		4.64
31.10.2018

What's New:

  • Updated this probe as part of removing dependency on the end-of-life (EOL) Microsoft Visual C++ Redistributables in CA UIM 9.0.2. CA UIM 9.0.2 now uses Microsoft Visual C++ Redistributable for Visual Studio 2017.
  • Updated this probe as part of removing known security vulnerabilities in CA UIM 9.0.2 by using the upgraded OpenSSL components.
MD5 Checksum: 860b0827ad1702672ef1d466b803f307
SHA-1 Checksum: 1af4e1dd807aac8d7ba8c29bbe1653f6823bbbb5 		4.63
05.09.2017

What's New:

  • Added support to monitor each instance of a process where the process is recognized by its name and process ID.

Fixed Defects:

  • The QoS interval time was slightly delayed for the processes state monitor. Support case number 781481

For Detailed Release Notes-Please refer to

https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN

Note: Support case(s) may not be viewable to all

md5sum: 7d7a32fb6213998d184d37bf97d8db33
sha1sum: 941de80dacfead7b6cd995ba3e6aecc9e681506d
4.60
23.05.2017

What's New:

  • (IM Interface only) Added support for:
    • AES-128 encryption
    • Monitor Windows systems where FIPS encryption is enabled

Important! In a FIPS encryption enabled environment, you cannot configure the probe from Admin Console (AC) interface.

For Detailed Release Notes-Please refer to

https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN

Note: Support case(s) may not be viewable to all

md5sum: 94e72cc61163fff189071ccd1d378e3a
sha1sum: 84c44b00d913aadb6c62098a06d16d5e8f41c72e
4.50
14.04.2017 What's New:
  • (Windows) Added support to monitor the symbolic links of a process using binary path.
  • (Windows) Added the useBackslashInProcOwner key that allows you to use "\" as the domain name separator while setting the process owner for a process.
  • (For HPUX only) Added the get_full_command_line key that allows you to view full command line parameters for a long process. For more information, see View Full Command Line Parameters. Support case number 632745
Fixed Defects:
  • The probe calculated incorrect QoS data. Support case number 472252
  • The probe generated lots of errors in the probe logs that resulted in flooding of the log file. Support case number 676172
md5sum: 418ba59e815afe1a8e3e3fa50da53f96
sha1sum: 6f693594a05d547fd13f173199f14a5b511d81c3
 4.40
23.09.2016 Fixed Defect:

1. The probe did not clear pending alarms in the following situations. Support case number 431592
    a. Any profile deleted or deactivated
    b. Any profile modified and saved without hard restart of the probe
    c. Probe upgraded with pending alarms of deactivated profiles. If you have already upgraded the probe, edit the profile and save the configuration.
2. The probe supports monitoring with an IPv6 environment.
   Important! The system, where CA UIM is installed, must be configured with dual stack (IPv4-IPv6).

For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN
Note: Salesforce case(s) may not be visisble to all
 4.32
24.05.2016 What's New:

(Solaris and HPUX) Added support to monitor the symbolic links of a process using binary path.
Added support to monitor binary paths of processes with command arguments.
Added support to expand the $process variable in MsgProcessInstances alarm with the binary path of processes.

For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN
 4.31
06.05.2016 What's New:
1. (Linux and AIX only) Added support to monitor the symbolic links of the process using binary path.

Fixed Defect:
1. On restarting, the probe removed the clone profiles from the Profiles list. Support case number 347255

For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN
Note: Salesforce case(s) may not be visisble to all 		4.20
11.04.2016 What's New:
(Linux and Solaris only) Added support to monitor the resident memory usage of the processes.

Fixed Defect:
1. The probe did not clear the pending alarms of the modified profile on soft restart. Support case number 312559
2. The probe did not start on Windows due to a dependency on vs2010 redistributable. Support case number 329119
The probe now requires vs2008.
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN
Note: Salesforce case(s) may not be visisble to all 		4.10
17.02.2016 What's New:

(For Linux only) Added the stack_size_in_mb key that allows you to search for processes using complex regular expressions. For more information, see Increase Stack Size. Support case number 246754

Fixed Defects:

1. The probe did not clear the "wrong process owner" alarm when process was started with the correct owner name.
Note: The probe will not generate the clear alarm if the threshold condition is no longer breached or probe is restarted for reason such as configuration changes. Support case number 245804
2. The probe crashed during a scheduled task and performed core dump. Support case number 70000540
3. The probe did not send alarms with the updated alarm severity. Support case number 00265085 (For Linux only) The probe crashed when complex regular expression was used to recognize a process. Support case number 246754
4. Updated the documentation to include the scenarios under which the alarm is generated during process up, down, or restart. For more information, see AC configuration or IM configuration articles. Support case number 246157
5. Updated the documentation to include the steps to stop truncation of more than 80 characters for Java process in Solaris platform.
For more information, see Remove Java Processes Character Truncation. Support case number 70001043

For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN
Note: Salesforce case(s) may not be visisble to all 		4.02
22.07.2015 Fixed Defects:

1. The probe was not using customized clear message text in ALARMS. Salesforce case 00163151
2. The probe was unable to monitor processes and generate alarms if the used memory was greater than 100 MB. Salesforce case 00162654
3. When the probe reported a PROCESS as down, it did not generate PROCESS down alarm with modified message text. Salesforce cases: 00161389, 00160183
4. Processes profile script was not executing properly. Salesforce case 00158405
5. On Unix platform, the QOS_Definition for the IPC counters QOS_IPC_SHARED_MEMORY_SEGMENTS_UTILIZATION, QOS_IPC_MESSAGE_QUEUES_UTLIZATION, QOS_IPC_SEMAPHORE_SETS_UTILIZATION and QOS_IPC_PROCESS_UTILIZATION sent an INCORRECT value for the hasmax field. Salesforce case: 00167456

For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN

Note: Salesforce case(s) may not be viewable to all 		4.01
15.06.2015 Upgraded OpenSSL to version 1.0.0m.
For Detailed Release Notes-Please refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN 		4.00
27.03.2015 Fixed a defect where all the eight IPC Counters were applying to template instead of two (Number of Processes' and 'Number of Semaphore Sets) for Windows OS.
Note
While upgrading the probe version from 3.83 to 3.92, process up and down alarms do not clear from alarm console automatically. User has to acknowledge these alarms manually.

For Detailed Release Notes- Please Refer
https://wiki.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=processes_RN 		3.92
23.03.2015 Added IPC Counter monitoring for Message Queues, Semaphores, Shared Memory Segments for Linux, Solaris, AIX, and Windows platforms.

Fixed Defects:
 1. Fixed a defect where the probe did not clear alarm from alarm console for CPU usage. (Salesforce Cases: 00155806, 00153144)
2. Fixed a defect where the probe did not clear the process up and down alarms. (Salesforce Cases: 00156008, 00156866, 00157484, 00154035, 00156940, 00156992, 00156510) .
Note
While upgrading the probe version from 3.83 to 3.91, process up and down alarms do not clear from alarm console automatically. User has to acknowledge these alarms manually.

For Detailed Release Notes- Please Refer
https://wiki.ca.com/display/UIMPGA/Process+Monitoring+%28processes%29+Release+Notes

3.91
06.02.2015 Fixed a defect where alarm was not getting cleared-Salesforce case 00146533

For Detailed Release Notes- Please Refer
https://wiki.ca.com/display/UIMPGA/Process+Monitoring+%28processes%29+Release+Notes

Note:Salesforce case(s) may not be viewable to all 		3.83
31.12.2014 Fixed a defect where only one process_down alarm was generating for all closed instances of a process. (Salesforce Case: 00135021)
Fixed a defect where suppression key is missing for process restart alarm, hence the alarm did not clear in the next interval. (Salesforce Case: 00143378)
Fixed a defect where the probe version 3.81 did not clear the process up alarms on the Admin Console, when the process was stopped. (Salesforce Case: 00146533)
Fixed a defect where the probe version 3.81 did not clear the Expected Instances alarms, when the process returns to the expected instance number. (Salesforce Case: 00148604)
Fixed a defect where the probe did not clear the alarms when the process returns to the expected instance number. (Salesforce Case: 00151678)

For Detailed Release Notes-Please refer
https://wiki.ca.com/display/UIMPGA/Process+Monitoring+%28processes%29+Release+Notes

Note:Salesforce case(s) may not be viewable to all 		3.82
10.10.2014 Fixed an issue where certain alarms were being suppressed on selecting the Track Processes by Process Identifier checkbox, while creating a profile. (Salesforce Case: 00144501)
For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/processes/ReleaseNotes/index.htm 		3.81
26.06.2014 Added support for zLinux Operating System. For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/processes/ReleaseNotes/index.htm 		3.80
16.04.2014 Fixed Defects: Fixed an issue where a message was not getting deleted from the message pool even when the user tries to delete the message without clicking Apply/OK. Fixed an issue where alarm is generated with the default text and not the modified text when the user edits the default MsgProcessRestart message, and restarts the probe and the process. For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/processes/ReleaseNotes/index.htm 		3.77
21.02.2014 Fixed a problem when user was not able to add custom messages with clear severity in the Message Override list.Fixed a problem when user was not able to get alerts with correct username (UID was getting displayed instead of username) when the username characters are more than 8. For Detailed Release Notes-Please refer
http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/processes/ReleaseNotes/index.htm 		3.76
29.11.2013 Fixed issue regarding probe defaults during upgrading the probe 3.75
08.11.2013 Probe default upgrade. Fixed memory leak issue on AIX. Fixed issue related to process name which starts with square bracket 3.74
27.06.2013 Fixed: Schedules generated incorrectly when crossing midnight. 3.73
10.04.2013 PS command thcount option replaced with nlwp for linux plateforms 3.72
10.01.2013 Fixed: GUI bug in processes related to exclude schedule. SOC Defects Fixed 3.71
14.09.2012 Functionality to use user/ruser in ps command for UNIX added. Added probe defaults. Fixed incorrect metric definitions. 3.70
06.06.2012 Fixed SOC Issues. 3.64
30.06.2011 Fixed an issue for process stop action alarm related to expanding $errmsg variable. 3.63
20.06.2011 Fixed hang situation on individual process monitoring.
 3.62
01.06.2011 High individual process CPU usage fix. 3.61
26.05.2011 Fixed incorrect cpu utilization issue.
Added support process handle count monitoring in Windows environment deployments. This feature is not applicable for non-windows platforms.
Added support for clearing alarms on restart for the profiles that are no more in the alarm state.
Fixed an issue related to $expected_user alarm variable expansion.
Added support for monitoring thread count for processes on AIX, LINUX & SOLARIS.
Added support for overriding QoS target at profile level.
Fixed a crash in thread count monitoring.
Fixed Service Oriented Configuration defect.
Additional error checking on fetching performance data.
3.60
21.01.2011 Added fixes for web-based Service Oriented Configuration.
Fixed CFX File.
 3.52
31.12.2010 Added option to limit processes seen to a configureable zone (Solaris).
Added support for internationalization.
Added support for reading alarm tokens from cfg.
Added support for Web-based Service Oriented Configuration (SOC).
Fixed memory leak.
3.51
13.08.2010 Applied fix to resolve the issue: TNT2 metric different for clear alarms.
Fixed Desktop Handle leak.
 3.40
14.04.2010 Applied a fix related to process name display on UNIX platforms. 3.30
14.04.2010 Fixed an issue related to process restart alarm.
Fixed ci_metric_type for minimum memory usage alarm. 		3.21
31.03.2010 Added support for extended NIS database information.
Added scheduler support for individual profiles’s QoS and Alarms.
Added support for action command on alarms for CPU profile.
3.20
19.03.2010 Added support for alarm clear when the monitored process goes down. 3.14
29.01.2010 Truncated process command line on windows to 4000 bytes. 3.13
20.10.2009 Added a fix to the data collector in the processes probe.

Alarm for incorrent instance not sent of the process is in the exclude list.
Added the missing MsgCpuUsageMin and MsgCpuUsageRange alarms to the cfx file.

Added support for LINUX_22.

Overwrite of subsystem ID for all alarms is now possible.
Handling of process names greater than 32 characters in case of Solaris.
Script execution on alarm conditions.
Fixed the exclude functionality. No alarms or QoS will be sent for processes that are excluded.
Support for $robot variable in messages.
Added 'default' flag for alarm messages.
Improved error handling for fetching performance data.

Added default clear message. Fixed configuration tool and probe to enable the use of the clear message.
Fixed minor GUI bug when using the new grouping of profiles feature. Sometimes, when the user double clicks a process in the status tab, and that profile is monitored by a profile, the profile would not be displayed unless the group were active and selected in the profiles tab.
3.12
29.04.2009 Added option to group profiles together. Group name can be used as part of alarm messages. Groups can be activated/deactivated without having to activate/deactivate all profiles within a group. Profiles can be moved between groups.

Added option to clone a profile (create a new profile with same settings as the source).

Added option to select many rows in profiles listbox.

Added option to 'track processes by process ID'. This opens up a new feature, to alert when a process has been restarted. It also opens the possibility to send in individual QoS samples for otherwise similar processes. Processes which you can't normally seperate using the standard methods like regexp or command line arguments.

Added option to monitor process instances between a given range.

Added option to alert if avg. cpu falls below a given threshold (similar as thread count and memory usage).

Added option to invert the test for process owner (to be able to alert when a process is NOT running under a given user). Easier than inverting a regexp method.

Fix: The GUI and the probe were treating the "proc_cmd_line" key differently which caused confusion. Probe accepted the string without the key "scan_proc_cmd_line", while the GUI did not. Now the GUI will interperet these keys the same way the probe does.

Fix: Improved various GUI input validation fields. Such as text fields which accept only numerical values should now only accept that.

Improvement: When the GUI is talking to a processes probe which runs on a Windows system, it will display both the working set (VM) and the pagefile memory in two seperate columns for processes.

Fix: Trailing blank space in command line arguments caused profile matching to fail on Windows platforms. 		2.90
19.12.2008 Rebuild following NimBUS library fixes. 2.73
20.11.2008 2.72
12.09.2008 Fixed configuration tool problems with renamed profiles.
Fixed shortcut keys for create and delete profile.
Fixed active state for on action input fields.
Added support for 64-bit Windows (x64).
Added support for LINUX on 64bit PowerPC (glibc = 2.3).
Added support for 64bit AIX, HP-UX, SOLARIS and LINUX.

Please note that, for version 2.71 and higher of this probe, NimBUS Robot version 3.00 (or higher) is a prerequesite. You are advised to carefully read the document "Upgrading the NimBUS Robot" before installing/upgrading.

2.71
12.10.2007 Windows: Program failure on > 4k command lines fixed.
 2.53
07.09.2007 Windows: Case independence of regular expressions fixed.
Windows: Command line process lookup improved for 32-bit processes.
Known issues:
The probe is unable to get the command line of 64-bit processes on Windows and of all processes on Windows Vista.
Since version 2.40, it is possible to try and retreive process information again if the probe believes the data to be corrupt. This limit has been defined to a default value of 1 (which means, try 1 more time and then give up). It can be tweaked in the raw-configure to any number between 0 and 10. 		2.52
25.05.2007 UNIX: Added new versions to supported platform list:
HPUX_11: 32bit (PA-RISC)
LINUX: 32bit (Glibc >=2.3)
SOLARIS_10: 32bit (x86)
Windows: Optimized code for fetching CPU usage per process. 		2.51
19.01.2007 Fix: Improved logic to try and detect corrupted process information on some rare situations on HPUX. If the probe detect corrupted data, there is a retry function that tries to retreive process information again.
Fix: The test button in the GUI, for testing a profile against running processes didnt respect the 'Excluded processes' list. This has been fixed.
Fix: The GUI sometimes didn't show if a process was being monitored, even if it the probe was monitoring the process. The reason for this was that the GUI was trying to match profiles against the process list from the probe. The process list returned to the GUI (from the probe) was a snapshot of current running processes. The process match against profiles logic has been moved to the probe, so the list displayed in the GUI should always show the processes that are actually being monitored by the probe. A process may also be monitored by more than 1 profile, which previous versions of the GUI was unable to handle.
GUI: New input field to allow custom log file size.
GUI: The help button in the dialog for Profile Monitoring dialog is now pointing to Profile setup in the documentation.
Fix: Probe should no longer be case sensitive on all windows platforms when matching process owner, process name or command line arguments.
GUI: Added a new menu item on the right-click context menu of the listview control that displays profiles. Prompts you to give a new profile name. If you select OK and the name does not already exist, the profile will be renamed once you save your config file.
GUI: The 'Expected Instances' field in the Profile Monitoring dialog has been changed to allow more processes. The limit has been increased from 999 to 9999.
Windows: skip commandline detection for 'System' process to avoid intermittent memory access violations. 		2.40
18.09.2006 Solaris: logging prints errno variable even when no error has occurred, making it seem as if there is a problem when there isn't.

Unix: Improved handling of child processes (fixes a problem with the signal handler hanging the probe in some cases)

Unix: Improved handling of forked processes 		2.35
09.02.2006 AIX: Fix problem getting the process list on v5.3 2.32
31.03.2005 Added process recognition by resource.

Message variables are made available to more alarm situations. The current set of variables is:
   arguments
   command
   description
   errmsg
   executable
   max_restarts
   pid
   proc_cmd_line
   process
   start_dir
   watcher
Instances
   instances_expect
   instances_found
   instances_op
   process_count
   process_count_type
Processes
   cpu_average
   cpu_total
   expected_cpu_usage
   expected_size
   expected_user
   max_samples
   op
   samples
   size
   thread_limit
   threads
   user
   time_delta
   which
Window
   window_name
   window_class
   window_text

 2.30
Requirements
Platform: Please refer to the Platform Support Matrix located in the Download section of http://support.nimsoft.com
Software: Version 2.71 and higher requires Nimsoft Robot 3.00 or newer.
Hardware: None