The SRE team's runbook for triaging production latency and error-rate incidents. Use this whenever investigating an incident, a latency spike, elevated error rates, or when asked "what caused X" about a production service.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
If you change the order below, say why in #sre.
p99_latency_ms / error_rate for the paged service. State the gap ("deploy 14:31, p99 moves 14:33").db_pool_utilization across checkout/cart/auth/inventory, then the upstream deps (db-primary, db-inventory, idp.internal). Find what moved first.Ask get_metrics for a name that doesn't exist and it lists the ones that do.
In rough order of how often:
One line at the bottom of your reply:
Root cause:
<sha>— one sentence on the mechanism.
If it wasn't a deploy, put the component or upstream dep where the sha goes (db-primary, stripe-api, whatever). Still one sentence.
Everything above that line is evidence. Keep it short; the long version goes in the postmortem doc.
If you were handed an incident id, also save the structured version to /workspace/findings/<INCIDENT_ID>.json so the postmortem can be built from it:
{
"incident_id": "INC-0000",
"service": "checkout",
"title": "one line, what users saw",
"root_cause": {"ref": "<sha or component>", "summary": "one sentence on the mechanism"},
"timeline": [{"time": "14:31:18", "event": "what happened"}],
"evidence": ["one fact per line, with the number or timestamp that proves it"],
"ruled_out": ["what you checked that turned out not to be the cause, and why"],
"impact": {"metric": "p99_latency_ms", "baseline": 65, "peak": 3640, "unit": "ms"},
"fix": "the immediate remediation",
"caused_by_incident": null
}
Set caused_by_incident to another page's id when your service is a victim of it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
How to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K/10-Q data, or company financials.
The English summary is being prepared. Showing the original description.
How to produce a demand forecast for a SKU, and when to delegate that to a subagent vs. compute it yourself. Load this for any task involving "forecast", "how much will we sell", "next month", promos, or seasonal SKUs.
The English summary is being prepared. Showing the original description.
Where diamonds spawn in Minecraft 1.20.
The English summary is being prepared. Showing the original description.
Fixed-format templates for Slack alerts, supplier emails, and escalations. Load this whenever the task is "notify", "alert", "email", or "tell ops".
The English summary is being prepared. Showing the original description.
How the SRE team writes a postmortem PDF. Use this whenever asked for a postmortem, an incident report, a write-up to share, or a PDF of what happened.
The English summary is being prepared. Showing the original description.
How to decide whether and how much to reorder a SKU. Load this whenever a task involves reorder recommendations, purchase orders, or "should we restock" questions.
The English summary is being prepared. Showing the original description.