Heartbeat Monitoring feature is available to Standard and Enterprise plans only. If you subscribed to a paid plan before October 14, 2016, you can refer Deprecated Heartbeats+ Separation for further information.
Heartbeat feature can be used to ensure that your environment is able to connect to OpsGenie continuously :
- There is no network problems between your system and OpsGenie
- Your heartbeat sender system is working as expected.
Heartbeat feature can also be used to monitor your periodic tasks are running as expected by using a suitable heartbeat expire interval regarding your periodic task run time.
When a heartbeat is added to OpsGenie with an interval of 10 minutes, your system is expected to send http based heartbeat requests periodically, at least every 10 minutes. If a heartbeat request is not received for more than 10 minutes, OpsGenie will conclude that there is a problem between your system and OpsGenie and create an alert according to your settings.
You can add any number of heartbeats to work. You can configure the check intervals for each heartbeat separately up to once per minute.
- Create a Heartbeat Integration from Integrations page, copy the API Key from that page
- Add your heartbeats from Heartbeats page, for each heartbeat define a unique name and select your desired interval. Without adding heartbeat you are not able to send heartbeat.
- You can also add heartbeats via Heartbeats API.
- Choose one of the following methods to send heartbeat to OpsGenie :
- Lamp, the command line utility can be easily called from any programming language, easy as : lamp heartbeat
- Heartbeats API , you may directly call REST API from any programming language
- OpsGenie Java API, if you are familiar with Java you can go with this option
- You can also use the Script Monitoring Client to automatically create and send heartbeat messages using a single command. The client is released for both Linux and Windows distributions. It's also a fit for monitoring one-time script jobs.
- Send Heartbeat policies, one of our new features, can also send heartbeat when a new alert is created in OpsGenie. Basically, you can turn alert creation into heartbeat monitoring with this policy.
- Make sure that your system sends heartbeats periodically at least every 10 minutes
- Make sure that your Heartbeat Integration & Hearbeat is enabled.
- Users that have Edit Configuration right can create and configure global or team-specific heartbeats using the Heartbeats page. On the other hand, team admins can create heartbeats that belong to their team and configure them.
- Create a Heartbeat Integration from the Integrations page
- You can select an owner team for the integration. Please note: You can assign at most one heartbeat integration to each team. Furthermore, you can configure at most one heartbeat integration that is not assigned to any team.
- Enter an Alert Message indicating heartbeat failures.
- If a heartbeat is expired or an expired heartbeat is pinged, heartbeat integration of the owner team is used while executing the related alert action (create, close, etc.). If the heartbeat that is expired or pinged is not assigned to any team, the global heartbeat integration (the heartbeat integration that is not assigned to any team) is used instead.
- From the Heartbeats page add a new heartbeat with a unique name and your desired expire interval.
- Send a heartbeat, open the Heartbeats page, it will show your latest active heartbeat.
- Wait until your last heartbeat expires do not send again, open Heartbeats page, it will show your latest expired heartbeat.
- An alert will be created soon after heartbeat expiry, notifying the recipients.
- Send another heartbeat, it will show your latest active heartbeat
- The expiry alert will be automatically closed soon