observability-planner

To design production observability, you plan structured metrics, events, dashboards, alerts, and SLOs tied directly to requirements. This enables per-requirement validation and incident-driven improvement for cloud-native systems.

Defining SLOs and alerts requires mapping governance objectives like SLO-XXXX and ALR-XXXX to specific requirements. This structured approach ensures alerts trigger incident feedback loops for continuous production improvement.

You create dashboards by building reference outputs that visualize both overall system health and per-requirement validation. These dashboards provide measurable visibility to detect and diagnose production incidents.

You need an observability plan during release activities at Gate 2 and beyond, as well as for continuous production operations. It establishes measurable visibility to detect, diagnose, and prevent incidents.

Yes, you can establish incident feedback workflows by defining governance around incidents and producing runbooks. This enables incident-driven improvement across cycles to continuously refine observability.

You start by creating an OBSERVABILITY_PLAN.md file outlining your MET-XXXX metrics, ALR-XXXX alerts, and SLO-XXXX objectives. This initial plan provides the structured foundation for your production service.