BackfillabOpsgenie heartbeats stopped after moving to Jira Service Management Standard? Here's how to fix it.
Last updated:
Native heartbeats in Jira Service Management are only available on the Premium and Enterprise plans, so a Free or Standard site has no heartbeat monitoring after you leave Opsgenie. You have three options: upgrade the site to JSM Premium, monitor your jobs with a separate external tool, or install Heartbeat Monitor for JSM, which brings heartbeats to Free and Standard sites inside Jira.
A heartbeat is a check-in that a scheduled job sends every time it runs: a nightly backup, a cron job, an ETL pipeline, a data sync. When the check-in stops arriving, something is broken, and nobody notices unless a tool is watching. Opsgenie shuts down on 5 April 2027, so teams moving to Jira Service Management need a new place for these checks.
The three options compared
| Upgrade to JSM Premium | External monitoring tool | Heartbeat Monitor for JSM | |
|---|---|---|---|
| Price | Premium plan price for the site, instead of Free or Standard (Atlassian pricing) | A separate subscription | Free for up to 3 monitors; paid licence for unlimited monitors through the Atlassian Marketplace |
| Setup | Change the site's plan, then configure heartbeats | New tool and account, then connect its alerts to Jira yourself | Install the app, create a monitor, add one HTTP call to your job |
| Where alerts land | Jira Service Management | The external tool, unless you integrate it with Jira | A Jira incident in the project you choose, plus notifications to the people you pick |
| Opsgenie import | Part of Atlassian's Opsgenie migration | Depends on the tool | One-click import of your Opsgenie heartbeats Beta |
Upgrading makes sense if you need other Premium features too. If heartbeats are the reason, the app keeps you on Free or Standard.
How Heartbeat Monitor for JSM works
- Know when a job silently stops. Every backup, cron job, ETL or sync gets its own ping URL. If the ping does not arrive on time, a Jira incident is created automatically and the right people are notified.
- One incident per outage. No duplicates, no noise. Incidents land where your team already works, in Jira, with priority and history.
- Recovery is handled for you. When the job checks in again, the app comments "recovered" and can resolve the incident automatically.
- Jobs can report failure. A job can call its URL with
status=failto raise an incident immediately.
Set it up step by step
- Install Heartbeat Monitor for JSM on your Jira Service Management site. As a Jira admin, open Settings > Apps > Heartbeat Monitor for JSM.
- Click Create monitor. Set how often the job should check in (every 5 minutes to every 24 hours) and a grace period, then choose the Jira project for incidents, the priority and the people to notify.
- Copy the monitor's ping URL and add one line at the end of your job. Examples for curl, PowerShell, cron and GitHub Actions are shown in the app. For a cron job:
0 2 * * * /opt/scripts/backup.sh && curl -fsS -m 10 --retry 3 "YOUR_PING_URL" > /dev/null || curl -fsS -m 10 --retry 3 "YOUR_PING_URL&status=fail" > /dev/null - Let the job run once. The monitor turns Up. If a check-in is late, it turns Late; if it is still missing after the grace period, the app opens a Jira incident.
- Coming from Opsgenie? Use Import my Opsgenie heartbeats Beta instead of step 2: paste an Opsgenie API key once and your heartbeats are recreated with the same names and intervals (intervals shorter than 5 minutes are set to 5 minutes). Then replace each old Opsgenie ping URL with the new one, using the checklist in the app.
Heartbeat Monitor for JSM is coming soon to the Atlassian Marketplace.
Ask for early accessFree plan: up to 3 monitors. Paid licence: unlimited monitors, failure reporting (status=fail) and automatic resolution.
Frequently asked questions
Why don't I have heartbeats in Jira Service Management Standard?
Native heartbeats in Jira Service Management are only available on the Premium and Enterprise plans. Free and Standard sites do not include them, so heartbeats you relied on in Opsgenie are not available on those plans.
Does Heartbeat Monitor for JSM work on JSM Free?
Yes. It brings heartbeat monitoring to any Jira Service Management plan, including Free and Standard. The free plan of the app includes up to 3 monitors.
How do I import my heartbeats from Opsgenie?
In the app, choose Import my Opsgenie heartbeats, paste an Opsgenie API key once and pick your region (US or EU). Your heartbeats are recreated with the same names and intervals, and you get a checklist to replace each old ping URL with the new one. The key is used once and never stored. The import is in beta, and Opsgenie shuts down on 5 April 2027.
What happens when a job misses its check-in?
The monitor turns Late. If the check-in is still missing after the grace period, the app opens one Jira incident in the project you choose and notifies the people you pick. When the job checks in again, the app comments that it recovered and can resolve the incident automatically.
Can a job report its own failure?
Yes. Add status=fail to the ping URL and the app raises an incident immediately, without waiting for the grace period. Failure reporting is part of the paid licence.
Where is my data stored?
The app runs on Atlassian Forge. Monitor settings and the last 50 events per monitor are stored in Forge storage on Atlassian's infrastructure. Ping payloads are not stored, except a short optional status note of up to 200 characters, and each ping URL carries its own secret token: a wrong token returns a plain 404. See the privacy policy.
How much does it cost?
The free plan includes up to 3 monitors. A paid licence, bought through the Atlassian Marketplace, adds unlimited monitors, failure reporting (status=fail) and automatic resolution of incidents.