Resolve heartbeat alerts
The Health Service sends a heartbeat to a management server to verify that the system is still responding. When a specified number of heartbeats fail to arrive, System Center - Operations Manager displays an alert.
This section shows how to investigate a Health Service Heartbeat Failure alert as an example. Different alerts have different causes and different resolutions.
If you want to walk through these procedures, you can cause this alert by disabling the Microsoft Monitoring Agent service on a test system.
To cause a Health Service heartbeat failure alert for testing
On a computer with an agent installed, open Control Panel.
Double-click Administrative Tools.
Double-click Services.
Right-click the Microsoft Monitoring Agent service, and select Stop.
Note
Use this same procedure and select Start in step 4 when you're done testing.
Investigate agent heartbeat issues
The Monitoring workspace displays active alerts. Looking at an alert provides information and tools to investigate with.
Investigate an active alert
Open the Operations console.
Select Monitoring.
Select Active Alerts to view the Health Service Heartbeat Alert.
Note
Depending on the heartbeat interval and the number of missing heartbeats, a few minutes might be required to see the alert.
Select the alert to highlight it and read the information in the Alert Details area. The Alert Details area provides information about the alert, including a description and knowledge about the cause and resolution.
Troubleshoot agent heartbeat issues
Use the tasks in the Tasks pane to diagnose the cause of the alert. Different alerts have different tasks. For a Health Service Heartbeat Failure alert, the tasks deal with pinging the system and verifying or restarting the service.
Use the action tasks in troubleshooting
In the Tasks pane, under Health Service Watcher Tasks, select Ping Computer. The task opens a dialog to display its progress.
Note
If the ping fails, use standard networking troubleshooting to figure out the issue with connectivity. Verify that the system is turned on.
Select Close to close the dialog.
Under Health Service Watcher Tasks, select Computer Management. A Computer Management dialog for the target system opens.
Select Services and Applications to expand it.
Select Services to display services.
Right-click the Microsoft Monitoring Agent service, and select Start.
Note
After the connection with the agent is restored, the alert will be automatically resolved and the computer status will return to healthy.
These steps will fix the test failure created in this article, and address many possible causes of a Health Service Heartbeat Failure. If an actual failure isn't resolved by these steps, use standard troubleshooting techniques to figure out the cause of the issue. For instance, the alert displayed in Active Alerts shows how old the alert is. Check for events that happened at this time to see what might have caused an issue.
A sudden increase in the number of alerts is called an alert storm. An alert storm can be a symptom of massive changes of some kind within your management group, such as a catastrophic failure of networks. An alert storm can also be a symptom of configuration issues within Operations Manager. A newly imported management pack starts monitoring immediately. If you have a large number of managed computers, an unforeseen configuration issue could cause a large increase in alerts.
Next steps
- Before changing the number of missed heartbeats allowed, first review How Heartbeats Work in Operations Manager.