Heartbeats for Jira Service Management
Get alerted when cron jobs, backups and pipelines silently stop, on any Jira Service Management plan. Each job pings a URL when it finishes. If a ping doesn't arrive in time, your on-call team gets a JSM alert, and the alert closes itself when the job recovers.
Install from Atlassian Marketplace
How it works
- Add a heartbeat in Jira settings → Apps → Heartbeats: a name, how often the job runs, a grace period and the alert priority.
- Copy its ping URL and call it at the end of the job, for example
curl -fsS -m 10 --retry 3 "<ping url>". - If the job goes quiet, Heartbeats raises one alert through your team's JSM API integration, so schedules and escalations apply. The next ping closes it.
Why teams use it
- Heartbeat monitoring in JSM normally needs Premium. This works on Free and Standard.
- Moving off Opsgenie (end of support April 5, 2027)? Keep your heartbeats without upgrading.
- One page lists every monitored job with its status and last ping.
- Nothing to host: it runs on Atlassian Forge.
Privacy and support
Heartbeats stores heartbeat definitions and your JSM integration key in Atlassian's Forge storage only. See the privacy policy and terms and the security policy. Questions: email support@norynta.com.