SAM 2019.4 using Real Time Process Explorer - triggered alerts not working for individual components

zennifer

I have a really weird situation that I discovered due to a failure.   We have a vendor specific application, I select the components to monitor thru the real time process explorer.   All has been working great in the previous version I was running.  It appears that after the upgrade in November the triggered alerts no longer work when a single process fails, however when all the processes fail, I get an alert for every process in a down state.

Any ideas?

We did upgrade the vendor specific application and Solarwinds at the same time because I was bored!

Below, there is a process called uedelta and mdtsrvr - one of each has stopped running, but SW does not present the downed service.   If I stop configinstaller, it does go to a down state and does send an alert.   

shuth

If you monitor a process that has multiple instances (e.g. the UeDeltaApp.exe), as long as ONE of those instances is running then SolarWinds will show the component as running.

If these processes use a different command line argument, you can filter by the command line for each process.

For example, the SolarWinds.BusinessLayerHostx64.exe has multiple instances but they use a different command line argument.

You can then configure the process monitor to filter on that command line argument. If you have 3 UeDeltaApp processes, you will have 3 components.

If they all use the same command line argument, you might be able to use something like the below methods and trigger if count < 3 ?

https://thwack.solarwinds.com/t5/SAM-Documents/Process-Count-Monitor/ta-p/517531

https://thwack.solarwinds.com/t5/SAM-Discussions/Counting-Instances-of-a-Process-Help/m-p/79888