- My View
Not my resolution, but I had looked this up before.
Let me know if this works for you. Please give the original poster (Berny Alvarado) of the solution an upvote if it works for you.
Personally, I have a PRTG external monitor that monitors the health of the MID, including all KHI's like CPU, Memory, Disk, and MID server service.
I attempt to restart the MID Server service a couple of times if it fails. I personally do not have the above solution deployed but wanted to just point you in that direction.
There is also the OOTB notification which is triggered by the mid_server.down event. There is a little information about this in the last paragraph of this page:
In earlier releases, the mid_server.down event would occur frequently if a MID server was busy because it would take a long time for heartbeat probes to be processed causing the status to be shown as 'down' when it actually wasn't. In later releases, the heartbeats have higher priority so the MID server processes them as soon as possible after receiving them so the false downs should be less frequent.
However, if you still find you get too many notifications, you might want to try Berny's method as Dan suggests.
Likewise. Thanks again for all your contributions. This community has been a great resource for me to continue to enjoy my free dev instance to work on SNOW event management so far.
I'm not sure and even not tried this but just come to my thought.
Why not to create email notification on table 'ecc_agent' and put condition whenever Status changes to Down and send the notification then.
Hope this helps.
If this post has helped, please choose 'Like', 'Helpful' or 'Correct'.