production-incident-responder

Manage a production incident response for a Kotlin Spring service by following a guided workflow that coordinates mitigation, diagnosis, communication, and evidence collection from the first alert through service restoration.

The best way to mitigate high error rates or latency spikes during a bad deploy is to apply the fastest reversible mitigation available, ensuring all rollback steps are auditable and well-documented to preserve evidence.

Incident response workflow preserves evidence and tracks timelines by implementing safety constraints that require reversible actions, document root-cause hypotheses, and maintain auditable incident notes throughout the process.

You can use this incident command workflow for capacity saturation or questionable config changes, as it applies to alerts of degraded latency, high error rates, and bad deploys by guiding disciplined stabilization and evidence collection.

You should not use automated incident mitigation when actions are not reversible or well-documented, as the workflow enforces safety constraints to ensure auditable rollback steps and preserve forensic evidence for root-cause diagnosis.