Integrations

PagerDuty + Outcome

Incidents from PagerDuty by service — how fast each is acknowledged and restored.

PreviewEngineeringStructureMeasuresSignals

What each brings

PagerDuty brings the facts. Outcome turns them into decisions.

UseFrom PagerDutyWhat Outcome does with it
Structure
  • Teams, people, reporting lines, cost centres, products and services
Each goal gets an owner, and each piece of work a team.
Measures
  • The numbers your goals are judged by
A goal's number is read on a schedule, with its history.
Signals
  • Feedback, calls, cases, incidents and usage patterns
Grouped into themes and put in front of the goal they bear on.
Works well with

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.

Setting it up

Connected in minutes, by an admin.

  1. 01Open

    An owner or admin opens Settings, Integrations, PagerDuty.

  2. 02Connect

    Paste: REST API key.

  3. 03Read

    Outcome reads it on the schedule you set, from the first day.

  4. 04Done

    Nothing is ever written to PagerDuty.

Full setup guide for customers

Where it is used

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