# PagerDuty/incident-response-docs

PagerDuty's Incident Response Documentation.

Repository: https://github.com/PagerDuty/incident-response-docs
Canonical: https://ross.abutalabs.com/products/incident-response-docs
Homepage: https://response.pagerduty.com
Language: Dockerfile
License: Apache-2.0
License Family: permissive
Topics: pagerduty, incident-response, documentation, oncall, team-security
Last push: 2026-07-02T15:10:20+00:00

## Health v2 (maintenance only)
Score: 73/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 90, release rhythm 35, longevity 100
- inputs: {"age_days": 3565, "days_push": 62, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1049, forks 220 (observed 2026-08-28T04:03:22.600922+00:00)

## What it is
PagerDuty's publicly shared incident response process documentation, published as a MkDocs static site. It covers on-call practices, incident severity levels, roles, and before/during/after incident procedures, and can be adapted by other organizations.

## Use cases
- set up an incident response process for my team
- train new engineers for on-call duties
- define incident severity levels
- learn what an incident commander does
- write postmortem and incident review templates
- establish on-call alerting principles

## When to choose
- you want a battle-tested, real-world incident response process to adapt
- you are onboarding engineers to on-call responsibilities
- you need reference material for incident roles, severity, and etiquette

## When to avoid
- you need incident management tooling or alerting software rather than process documentation
- you need compliance-focused security incident response (e.g. SOC/forensics) guidance
- you want an automated or integrated incident platform

## Facets
- artifact type: learning-resource
- maturity: active
- function: documentation, monitoring, alerting
- domain: documentation, monitoring, developer-tools
- platform: self-hosted
- tags: incident-response, on-call, mkdocs, sre, postmortem, severity-levels, incident-commander, devops, web-server, docker

## Member repositories
- PagerDuty/incident-response-docs (main) score 73

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:22.600922+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:00:27.575638+00:00, confidence not recorded.
  - readme: https://github.com/PagerDuty/incident-response-docs (fetched 2026-08-28T04:03:22.600922+00:00, sha 740c96de38f3)
  - homepage: https://response.pagerduty.com (fetched 2026-08-29T13:01:45.867219+00:00, sha 34ade57d26e1)
  - site_page: https://response.pagerduty.com/about (fetched 2026-08-29T13:01:45.869754+00:00, sha 6b099a635436)
- Data as of 2026-08-30T08:39:29.467469+00:00.