[::] Agentic Stacks

Reference: Incident Response Agent

reference

ops-incident-response

framework
Agent Framework
memory
Memory
retrieval
Retrieval / Vector Store
observability
Observability / Tracing
deployment
Deployment Target
mcp_servers
MCP Servers
guardrails
Guardrails / Safety

Architectural notes

Reference architecture for an on-call agent that triages PagerDuty alerts,
pulls context from Datadog/logs/recent deploys, drafts an initial
diagnosis, and routes to the right on-call human.

Why these picks:
- Haiku for fast triage classification; Sonnet for diagnosis writeups.
- Memory holds postmortems and "the last time this fired" context.
- GitHub MCP correlates recent deploys with alert times.
- Read-only by default; write actions (acks, rollbacks) require human approval.

Common gotchas:
- False-positive auto-responses worse than no response; bias toward
  "summarize + escalate."
- Postmortem corpus is the single biggest accuracy lever.

Embed this stack

Show off your stack on your engineering blog or company page.

<iframe src="http://testserver/embed/stacks/ops-incident-pagerduty" width="100%" height="380" frameborder="0" style="border: 1px solid #334155; border-radius: 8px;"></iframe>
Preview embed

Share

Similar stacks

Get the weekly digest

New stacks, new tools, what's moving. No spam.