OpenAna + PagerDuty

Incidents, alerts and on-call schedules, connected to your monitoring tools.

Live connectionIncident & ITSM

Ana + PagerDuty

What Ana does with it.

Alerts and incidents Ana picks up, investigates and resolves with on-call approval.

01
Starts investigating the moment a page fires
02
Posts findings and remediation for on-call approval
03
Drafts the timeline and post-incident review

Setup

Connected in four steps.

1
Connect
Open Integrations in Ana and connect PagerDuty with a scoped token, OAuth app or service account.
2
Scope it
Start read-only and choose which projects, repositories or accounts Ana can see.
3
Set the rules
Decide which actions need approval and who approves them - Ana’s guardrails enforce it.
4
Put it to work
Ana uses PagerDuty in investigations, fixes and reports, and every action is logged.

In practice

Playbooks that use PagerDuty.

SRE / DevOps

From a 3 a.m. page to root cause and fix

An alert pages the on-call engineer. By the time they open the laptop, Ana has correlated metrics, logs, traces and recent deploys, named the likely cause, and drafted the remediation for approval.

Read the playbook →

Used by

Ana’s engineers

SRE / DevOps →

Governed

Every action, approved and logged.

Ana’s guardrails decide what it may do with PagerDuty, route sensitive actions to named approvers, and keep evidence for each decision. OpenAna is SOC 2 Type II, ISO 27001, HIPAA and GDPR compliant.

Guardrails →Trust center →

FAQ