Integration · APM & alerting
Opsgenie
Heartbeat plus alert API.
What gets collected
Heartbeat checks run alongside alerts. Escalation routing is handled on the Opsgenie side.
Requirements
- ✓Integration API key
- ✓team mapping per severity
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
opsgenie.alerts.createdopsgenie.heartbeat.stateopsgenie.ack.latencySetup steps
- 1Integration API key
- 2Team mapping per severity
After install
- · Metrics show up on the dashboard within 15-30 seconds
- · Integration labels flow into filters automatically
- · Dashboard presets for common metrics are available in the editor
More in the docs
Opsgenie
Frequently asked questions
- What does Unimoni collect from Opsgenie?
- Heartbeat plus alert API. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across Opsgenie and everything else in one place.
- How long does it take to connect Opsgenie?
- Usually a few minutes: a handful of steps, no code changes. Metrics show up on your dashboards within 15–30 seconds of the first scrape.
- What access does the Opsgenie integration need?
- Only the minimum listed under Requirements above — a scoped token or role, nothing more. Unimoni asks for the least privilege each system supports.
- Is Opsgenie monitoring available self-hosted and on the free plan?
- Yes. Every integration works identically on Unimoni Cloud and self-hosted, and is included from the free tier up.