Hello,

 

Windows and UNIX process monitors used to work where you could add them and when they went down and came back up, OpManager would record that they went down and came back up. Now, when a server is restarted (for example), the process monitors still show them as down when the processes are actually up. I am assuming this is because the process IDs changed.

 

The documentation for OpManager states that we can track processes via path and arguments as well as the number of instances. No mention is made of PID. We are using OpManager 8 (build 8007) and this issue has been since we first migrated from version 7 to version 8.

 

On many of ourmonitored hosts, we really want to monitor processes but are unable to do so because OpManager doesn't show them running when they are restored from a restart or failure. See attached image for an example of Windows Monitors that show down after a server reboot but are actually running on the server.

 

Regards,

 

LeRoy