What is the best way to monitor Mid server's status?

[kumaraj]

Hi Guys,

 I can see there is default Notification and events available already.

I have just put my email id and observe that i got the email when MID server was down but not when it is up, however I put both the condition in Notification.

1st query is : What would be the best way to monitor Mid server? How the available mid server events are used with it's notification. I do not see any default relation between events and notification.

2nd Query: As i read that by default a heartbeat goes to mid server in every 5 minutes to see if it response back, but when i open the heartbeat prob then

I do not understand that how it is communicating with mid server . I dont see any such configuration in Heartbeat prob like which mid server/what should be frequency to run hearbeat? No hints i get,

So someone please address it in provide me the solution.

[SanjivMeher · Accepted solution]

I would suggest setting up notifications when mid server goes down or comes back online.

Also set up a Cluster MID server for high availability. So that when one MID Server goes down, the other one becomes active.

[Patrick DeCarl1]

Check out links below https ://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/product/mid-server/reference/r_MIDServerHeartbeat.html https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/product/mid-server/concept/c_MIDServerDashboard.html

[tim_broberg]

For the first, the business rule "MID - Heartbeat" detects a heartbeat probe input and sets ecc_agent.status = "Up".

Business rule "Agent status monitor" detects the change of agent status, handling both the up and down events. He should see the change of ecc_agent.status and enqueue an event. If you're seeing down events, then both kinds of events are being enqueued. Somehow, you're not catching the "up" events.

Regarding the second, Heartbeat probes are created assigned to mid agent "mid.server.*".

A business rule detects ecc_queue outputs with agent = mid.server.* and creates one copy of the probe addressed to each mid server.

(There is a significant limitation to the heartbeats, by the way: they are all assigned to priority 0. The mid server currently has a separate thread pool for each of the three priority levels. If every thread in the priority 2 pool dies, discovery and activities will not be serviced, but the heartbeats will continue.)

Hope this helps,

    - Tim.