MID Server heartbeat
The instance checks the MID Server for a response every 5 minutes, using a synthetic transaction monitoring system.
Checking for a heartbeat
ServiceNow instances send a synthetic transaction via the Heartbeat probe to every MID Server every 5 minutes. The Heartbeat probe functions exactly as a normal probe does and is sent by writing an output record to the ECC queue. A MID Server retrieves the record when it queries the ECC queue for work. The MID Server processes the probe just as it would any other probe and responds back to the instance. If the instance does not detect a response from a MID Server, the instance marks that MID Server as Down. If the MID Server responds, the instance considers the MID Server to be functioning and communicating properly with the instance.
System events
- mid_server.up: The MID Server goes from a status of Down, Paused, or Upgrading to a status of Up.
- mid_server.down: The MID Server goes from a status of Up to a status of Down.
- mid_server.paused: The MID Server is paused.
- mid_server.upgrading: The MID Server is being automatically upgraded because the instance is being upgraded.
You can use these events to send notifications or trigger actions that you specify in scripts.