Processes Probe Fails to Clear Alarms for Processes with Unique Session IDs

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

 The Processes probe in DX Unified Infrastructure Management (UIM) fails to clear "Process Not Found" alarms, after the process has restarted. This typically occurs when the process command line includes a unique session ID or a dynamic pipe name that changes upon restart.

Example:

c:\windows\system32\inetsrv\w3wp.exe -ap "AdditionalServices" -a \\.\pipe\iis<session ID> 

Resolution

 To resolve this, you must modify the process profile in Infrastructure Manager (IM) to use wildcards and escape characters. This allows the probe to match the process regardless of the unique session ID.

1. Escape Backslashes: Double every backslash (\) in the path to ensure the probe treats them as literal characters.

2. Use Wildcards: Replace the unique or dynamic portion of the command line with an asterisk (*).

Original (Failing):
c:\windows\system32\inetsrv\w3wp.exe -ap "AdditionalServices" -a \\.\pipe\iis<session ID> 

Corrected (Working):
c:\\windows\\system32\\inetsrv\\w3wp.exe -ap "AdditionalServices" -a \\\\.\\pipe\\iisipm*