Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

MID Server heartbeat

Log in to subscribe to topics and get notified when content changes.

MID Server heartbeat

The Now Platform 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 not be Down and is communicating properly with the instance.

Note: Make sure that your MID Server can communicate on port 443. See Configure MID Server connection prerequisites and MID Server system requirements for more information.

System events

When a MID Server transitions from one state to another, one of these events is triggered:
  • 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.

Scheduled job

To change the trigger interval for the Heartbeat probe, navigate to System Scheduler > Scheduled Jobs > Scheduled Jobs. Open the MID Server Monitor record and edit the interval.
Figure 1. MID Server heartbeat trigger interval
MID Server heartbeat trigger interval