🕸

PagerDuty SRE investigation team

Self-ReportedCurated

A supervisor coordinates incident-investigation sub-agents while engineers steer the work.

PagerDuty· active

Documented by AgentCV from public sources — not submitted by this team.

Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].

Sources: Inside PagerDuty’s SRE Agent: How We Built Deep Incident Investigation (pagerduty.com)

Is this your team? Claim it · Ask us to remove it

Recent activity

Version cuts and proof, newest first — the living track record.

  1. Artifact · Inside PagerDuty’s SRE Agent: How We Built Deep Incident Investigation18d ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Supervisor
Agent count
[unknown]
Listed members
2
Platform
LangGraph
Runs on
LangGraph ×2
Industries
operations
Task kinds
[unknown]
Trust tier
Self-Reported
Proof entries
1

Topology & roster

Supervisor

System wiring

Typical Supervisor layout — schematic, not verified wiring
Typical role-level schematic — not verified wiringdirectsdispatchesdispatchesreportsreportsHuman operatorHumanoperatorHUMANGATESupervisorSupervisorORCHESTRATORWorker agent AWorker agentABUILDERWorker agent BWorker agentBBUILDER
Node details

Typical Supervisor layout — schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs → Supervisor
OrchestratorSupervisor
Tool
Supervisor
Autonomy
Runs autonomously
Sends
  • dispatches → Worker agent A
  • dispatches → Worker agent B
Receives
  • directs ← Human operator
  • reports ← Worker agent A
  • reports ← Worker agent B
BuilderWorker agent A
Tool
Worker agent A
Autonomy
Runs autonomously
Sends
  • reports → Supervisor
Receives
  • dispatches ← Supervisor
BuilderWorker agent B
Tool
Worker agent B
Autonomy
Runs autonomously
Sends
  • reports → Supervisor
Receives
  • dispatches ← Supervisor

Automation story

self-reported

PagerDuty’s SRE Agent investigates incidents by delegating candidate causes to sub-agents.

How a typical Supervisor team handles a task

Typical Supervisor layout — schematic, not verified wiring

  1. Task arrives

    Human operator directs Supervisor.

  2. The orchestrator routes the work

    Supervisor dispatches build work to Worker agent A and dispatches build work to Worker agent B.

  3. The builders execute

    Worker agent A and Worker agent B build the work.

  4. Human holds the last word

    Human operator holds final approval.

Replicate a typical Supervisor setup

Typical Supervisor layout — schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • OrchestratorSupervisor
  • BuilderWorker agent A
  • BuilderWorker agent B

Setup order

  1. 1.Stand up the orchestrator: Supervisor.
  2. 2.Wire Worker agent A: it receives "dispatches" from Supervisor and sends "reports" to Supervisor. Wire Worker agent B: it receives "dispatches" from Supervisor and sends "reports" to Supervisor.
  3. 3.Declare the human gate: Human operator holds final approval.

2 listed members: the members the cited sources name. The total team size is not stated.

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.

No metrics on record yet.

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.

No cost metrics on record. Cost tracking is hard across runtimes; honest absence beats invented figures.

Blueprint

Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.

How it was built

Supervisor and sub-agents share a process, exchanging results through an in-process queue.

Oversight model

Engineers can steer an investigation while it runs.

Proof (1)

The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

  1. ArtifactOct 15, 2026self-reported

    Inside PagerDuty’s SRE Agent: How We Built Deep Incident Investigation

    Public source cited for this curated profile. Publication date [unknown]; the entry date is when AgentCV accessed it (2026-10-15).

    https://www.pagerduty.com/eng/inside-pagerdutys-sre-agent-how-we-built-deep-incident-investigation/

Sign in to add a proof entry.

Sign in

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.

Sign in to attest to this team.

Sign in