/PostmortemMicroservicesSystem
Draft a blameless postmortem for a microservices system — e.g. a system of eight services with no shared tracing.
Your AI Command Vault
Running on hopes, dreams, and GPUs.
IncidentResponse
36 commands
Draft a blameless postmortem for a microservices system — e.g. a system of eight services with no shared tracing.
Investigate the root cause of an incident in synthetic monitoring checks — e.g. a critical user flow with no automated uptime checks.
Draft a blameless postmortem for a failed deployment needing rollback — e.g. a bad deploy causing a spike in 500 errors.
Write an incident runbook for a database outage — e.g. a primary database that failed over unexpectedly.
Investigate the root cause of an incident in a memory leak in a running service — e.g. a service whose memory grows steadily over 24 hours.
Draft a blameless postmortem for an error budget and slo setup — e.g. a service with no defined slo or error budget.
Write an incident runbook for a latency spike — e.g. an api whose p99 latency tripled overnight.
Investigate the root cause of an incident in a production outage — e.g. a two-hour checkout outage during a sale.
Draft a blameless postmortem for synthetic monitoring checks — e.g. a critical user flow with no automated uptime checks.
Write an incident runbook for a security incident — e.g. unusual access patterns detected on an admin account.
Investigate the root cause of an incident in a capacity planning exercise — e.g. a service expecting 10x traffic during a launch.
Draft a blameless postmortem for a memory leak in a running service — e.g. a service whose memory grows steadily over 24 hours.
Write an incident runbook for an on-call rotation process — e.g. an on-call rotation with unclear escalation paths.
Investigate the root cause of an incident in a centralized log pipeline — e.g. logs scattered across ten unindexed servers.
Draft a blameless postmortem for a production outage — e.g. a two-hour checkout outage during a sale.
Write an incident runbook for a microservices system — e.g. a system of eight services with no shared tracing.
Draft a blameless postmortem for a capacity planning exercise — e.g. a service expecting 10x traffic during a launch.
Write an incident runbook for a failed deployment needing rollback — e.g. a bad deploy causing a spike in 500 errors.
Investigate the root cause of an incident in a database outage — e.g. a primary database that failed over unexpectedly.
Draft a blameless postmortem for a centralized log pipeline — e.g. logs scattered across ten unindexed servers.
Write an incident runbook for an error budget and slo setup — e.g. a service with no defined slo or error budget.
Investigate the root cause of an incident in a latency spike — e.g. an api whose p99 latency tripled overnight.
Write an incident runbook for synthetic monitoring checks — e.g. a critical user flow with no automated uptime checks.
Investigate the root cause of an incident in a security incident — e.g. unusual access patterns detected on an admin account.
Draft a blameless postmortem for a database outage — e.g. a primary database that failed over unexpectedly.
Write an incident runbook for a memory leak in a running service — e.g. a service whose memory grows steadily over 24 hours.
Investigate the root cause of an incident in an on-call rotation process — e.g. an on-call rotation with unclear escalation paths.
Draft a blameless postmortem for a latency spike — e.g. an api whose p99 latency tripled overnight.
Write an incident runbook for a production outage — e.g. a two-hour checkout outage during a sale.
Investigate the root cause of an incident in a microservices system — e.g. a system of eight services with no shared tracing.
Draft a blameless postmortem for a security incident — e.g. unusual access patterns detected on an admin account.
Write an incident runbook for a capacity planning exercise — e.g. a service expecting 10x traffic during a launch.
Investigate the root cause of an incident in a failed deployment needing rollback — e.g. a bad deploy causing a spike in 500 errors.
Draft a blameless postmortem for an on-call rotation process — e.g. an on-call rotation with unclear escalation paths.
Write an incident runbook for a centralized log pipeline — e.g. logs scattered across ten unindexed servers.
Investigate the root cause of an incident in an error budget and slo setup — e.g. a service with no defined slo or error budget.