Incident Postmortem
Gather error timeline, logs, and resolution steps into a postmortem document
Example Prompt
Create a postmortem for the payment service outage that happened last night
About
Automatically compiles a comprehensive incident postmortem by pulling error events from Sentry, retrieving container logs from Docker, and reasoning through the root cause timeline. The final postmortem document is written to the filesystem with a structured format including timeline, impact, root cause, and action items.
Workflow Steps
List recent critical issues from Sentry to identify the incident timeline
🚨 List IssuesRetrieve detailed event data for each critical issue to understand error context
🔍 Get Error EventPull container logs from the affected services during the incident window
📜 Container LogsReason through the collected evidence to determine root cause and contributing factors
🧠 Structured ReasoningWrite the structured postmortem document with timeline, impact, root cause, and action items
✏️ Write FileTools Used
Container Logs
Retrieve log output from a running or stopped Docker container
Write File
Write or overwrite a file at a specified path with the given content
Get Error Event
Retrieve detailed information about a specific Sentry error event including stack trace
List Issues
Retrieve unresolved error issues from a Sentry project, sorted by frequency or last seen
Structured Reasoning
Break down a complex problem into sequential reasoning steps with explicit chain-of-thought
Required MCP Servers
Docker
Manage containers, images, volumes, and networks via the Docker daemon
Filesystem
Read, search, and manage files on the local filesystem
Sentry
Query error reports, performance data, and release health from Sentry
Sequential Thinking
Dynamic problem-solving through structured thought sequences with branching and revision