Integration · APM & alerting
PagerDuty
Two-way channel: notifications plus acknowledgements back.
What gets collected
Events API v2 for sending plus a webhook to receive acks. Severity maps automatically to P1/P2/P3.
Requirements
- ✓Events API v2 routing key
- ✓webhook for ack
- ✓service integration
Key metrics
Collected out of the box. Every metric is available in dashboards, alerts and PromQL.
pd.incidents.triggeredpd.ack.latencypd.escalationspd.resolve.timeSetup steps
- 1Create an integration in a PagerDuty service
- 2Routing key in the channel config
- 3Webhook URL for ack feedback
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
PagerDuty
Frequently asked questions
- What does Unimoni collect from PagerDuty?
- Two-way channel: notifications plus acknowledgements back. Every metric lands in the same TSDB as the rest of your stack, so you can build dashboards and alerts across PagerDuty and everything else in one place.
- How long does it take to connect PagerDuty?
- 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 PagerDuty 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 PagerDuty 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.