Observability Design Review

Review logging, metrics, tracing, context propagation, SLO/SLI, alerts, dashboards, sampling, retention, privacy, and cost designs before implementation. It produces OBS-## findings and validation preparation; it does not read runtime signals to declare health or choose SLO/incident severity.

When to Use

• Use it to check whether signal fields/dimensions, semantics, correlation IDs, sampling, retention, and alerts are actionable.
• Use it to identify sensitive-data, cardinality, alert-noise, blind-spot, and cost risks.
• Use it when runtime data is unavailable and the telemetry design itself needs review.

Do not use it to query production logs, execute probes, analyze a real incident, or declare system health.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use