incident-response

Structured incident response requires collecting logs, metrics, traces, and recent changes across affected tenants. This skill guides that evidence gathering process, followed by 5 Whys analysis to identify root causes for outages or degraded functionality.

A blameless postmortem documents lessons learned and action items without attributing fault to individuals. This skill generates blameless postmortems automatically after you complete the incident investigation workflow.

Investigating security events or degraded functionality across tenants requires a stepwise workflow: assess impact, collect evidence, perform root-cause analysis, implement minimal fixes, and verify in staging before deploying with monitoring.

The best way to structure incident investigations is following a sequential process: assess impact, gather evidence from logs and traces, perform 5 Whys root-cause analysis, implement minimal fixes, verify in staging, and deploy with active monitoring.

Yes, this incident response workflow applies to outages, degraded functionality, and security events across one or more tenants. The structured steps guide assessment, evidence collection, root-cause analysis, and blameless postmortem creation for any incident type.

Incident response processes lack consistent postmortems when no structured workflow captures lessons learned and action items. This skill standardizes blameless postmortem generation after guiding evidence collection and 5 Whys root-cause analysis.