PagerDuty + Outcome
Incidents from PagerDuty by service — how fast each is acknowledged and restored.
PagerDuty brings the facts. Outcome turns them into decisions.
| Use | From PagerDuty | What Outcome does with it |
|---|---|---|
| Structure |
| Each goal gets an owner, and each piece of work a team. |
| Measures |
| A goal's number is read on a schedule, with its history. |
| Signals |
| Grouped into themes and put in front of the goal they bear on. |
PagerDuty + Atlassian + Outcome
What it never reads
- Writes of any kind to PagerDuty
Status
Preview Engineering
Live In the product today. Preview Working, refined with customers.
Connected in minutes, by an admin.
- 01Open
An owner or admin opens Settings, Integrations, PagerDuty.
- 02Connect
Paste: REST API key.
- 03Read
Outcome reads it on the schedule you set, from the first day.
- 04Done
Nothing is ever written to PagerDuty.
Connect PagerDuty and see what it brings in on the first sync.
Also in engineering Atlassian · GitHub · File import · Sentry · ServiceNow · Azure DevOps · GitLab · Linear