common-troubleshooting

Troubleshoot vague PostgreSQL failures on Kubernetes by applying a hypothesis-driven, seven-step workflow that defines the problem, refines hypotheses, confirms root causes, and outputs a structured RCA for repeatable cross-cutting investigations.

A hypothesis-driven RCA framework enforces mandatory checkpoints across a seven-step process, moving from symptom classification to root-cause confirmation and prevention reporting while delegating evidence gathering to ensure traceable database investigations.

Yes, you can use this workflow for connection, storage, and performance issues in Kubernetes-managed PostgreSQL clusters. It handles cross-cutting failures by enforcing mandatory checkpoints and documenting evidence across multiple investigation areas.

Start an investigation by completing Step 1: Problem Intake. The workflow then recommends specific skills to gather evidence and validate hypotheses, progressing through focused checks and root-cause confirmation to generate a documented RCA.

Use a structured RCA workflow when problems are vague, span multiple areas like connections and storage, or require a documented investigation trail across a Kubernetes-backed PostgreSQL stack. It enforces repeatable, traceable checkpoints over ad-hoc debugging.