Heartbeat monitoring approach is complementary to other monitoring tools, addressing use cases where usual approach of active checks or listening for problems does not work.
Instead of waiting to hear for bad news, heartbeat monitoring expects to receive good news. If a heartbeat message indicating successful completion of a task is not received within specified intervals, an alert is generated and the relevant people are notified.
Define when something should happen. A heartbeat configuration indicates how often OpsGenie should expect to receive a heartbeat message.
Send heartbeat messages to OpsGenie when it happens. OpsGenie keeps track of the heartbeat messages, when last heartbeat is received, when it will expire, etc.
Get notified if no hearbeat is received within specified interval. Heartbeats monitors generate alerts in OpsGenie, and users are notified according to the defined policies & preferences, via email, SMS, phone and push notifications.
How would you find out if (when?) your monitoring tools themselves are not working? OpsGenie customers configure their monitoring tools to send periodic heartbeat messages to OpsGenie. If OpsGenie does not receive any heartbeat messages within the expected time frame, an alert is generated and specified people are notified about the problem.
Periodic jobs such as daily backups, file transfers, and reports can be difficult to monitor using usual monitoring tools. Heartbeats support providing heartbeats for your periodic jobs and specify the interval they should run. If OpsGenie does not receive the heartbeat message that would indicate successful completion of a job, an alert is created and the relevant people are notified. In addition, Heartbeats dashboard shows the state of each of the configured heartbeats, so you can see the status of all your periodic jobs, the time they were last executed successfully, etc. in one place.
Keep track of when manual tasks are executed. Heartbeats dashboard (and API) displays the date & time the last heartbeat message was received, and when the next one is expected to be received. Execution of ad-hoc tasks can be tracked by sending heartbeat messages when they are executed.