MID Server heartbeat
-
- UpdatedAug 1, 2024
- 2 minutes to read
- Xanadu
- MID Server
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.
Scheduled job
Related Content
- MID Server system requirements
Use these minimum system requirements to allocate resources for computers hosting MID Servers.
- MID Server upgrades
Upgrade MID Servers manually, or automatically through the instance. MID Server automatic upgrade is triggered when the instance upgrades and the MID Server no longer has the same version. The new MID Server package is downloaded from install.service-now.com, replaces the old one, and the MID Server starts with the new version.
- Resolving MID Server issues
Troubleshoot problems with the MID Server to find solutions. Monitor the MID Server to receive alerts about issues as they occur. Troubleshooting procedures exist to resolve specific problems with the MID Server. The Knowledge Base on Hi contains several articles to help you troubleshoot MID Server issues.
- MID Server dashboard
The MID Server dashboard is a central place for MID Server users to monitor ongoing operations. The dashboard consists of reports and gauges that display information from the MID Server Status table.
- MID Server properties
Properties control the behavior of all MID Servers or a particular MID Server.
- MID Server parameters
Parameters control the behavior of a particular MID Server and have lower precedence than MID Server properties.
- MID Server Configuration Parameter settings and priority
The MID Server's settings reside in multiple tables and the MID Server prioritizes them in a set order. MIDConfigParameter must be defined with the correct type-style builders.
- MID Server File Cleaner
A monitor thread runs in the MID Server to clean up old files, to keep the size and quantity of files within the install folder manageable, and to prevent performance issues with the MID Servers.
- MID Server protected records and reserved characters
Some MID Server records cannot be altered. Certain special characters are pre-defined in XML and cannot be used in passwords.
- MID Server privileged commands
To discover certain information on a host server, the MID Server must run SSH commands with higher privileges. The platform provides default privileged commands for the MID Server to use and the ability to add additional commands to the system.
- MIDSystem methods
MIDSystem variables (referred to by the variable name ms.) provide a variety of methods to get information about the MID Server.
- Manually start, stop, and restart a MID Server
If you did not start the MID Server at the end of the installation procedure, you can manually start the MID Server.
- Set the MID Server JVM memory size
The MID Server starts with a default JVM memory allocation, but you can modify this setting in the configuration file.
- Pause the MID Server
Pause the MID Server to temporarily prevent it from polling the ECC Queue for work or sending Discovery results back to the instance.