Atlassian-shop on-call
If you already use Jira, Confluence, and Statuspage, Opsgenie is the natural on-call layer. Uptimera plugs in without you having to re-pick a vendor.
On-call integration
Forward Uptimera incidents to Opsgenie via API integration. Opsgenie's schedules, escalations, and routing rules take over from there — same model as the PagerDuty integration, for teams that standardized on the Atlassian on-call stack.
Availability: Available on Pro and Business plans.
In Opsgenie, Teams → your team → Integrations → "Add integration" → "API". Copy the API key.
In Uptimera, Settings → Alert Channels → "Add Opsgenie". Paste the API key and select the default priority (P3 is a reasonable starting point).
Set the Opsgenie channel as a target on your production monitors. Staging and side-project monitors can stay on Slack/email — pages should be reserved for things that actually need a human.
Use "Send test alert". Verify the alert lands in Opsgenie at the priority you expected and routes through your on-call schedule.
If you already use Jira, Confluence, and Statuspage, Opsgenie is the natural on-call layer. Uptimera plugs in without you having to re-pick a vendor.
Route different monitors to different Opsgenie teams — the API monitor pages the backend team, the marketing site pages the web team.
Uptimera closes the Opsgenie alert when the service recovers, so on-call doesn't have to manually clear stale alerts.
Yes. The default priority is set on the integration, but each monitor can override it. Production database checks at P1, marketing site at P3, etc.
Yes — you can configure responders (team, schedule, user) per monitor. Uptimera passes them through to the Opsgenie alert create API.
Atlassian announced Opsgenie's end-of-life with migration to Jira Service Management. Uptimera will support both during the transition window and will publish a migration guide closer to Opsgenie's sunset date.
Connect Opsgenie to Uptimera in under 2 minutes. Free plan included.