Contract

• Input: system architecture, user journeys, critical paths, available telemetry.
• Output: SLI/SLO spec + dashboard design + alert rules + runbook.
• Side effects: none (design only; execution requires access to telemetry platform).
• Dependencies: telemetry platform (Prometheus / Grafana / Datadog / CloudWatch / New Relic / Jaeger).
• Stop condition: all outputs saved.
• Risk: medium — wrong alerts cause fatigue or miss critical events.
• Boundary: defines observability; does not configure production alerts alone.

SRE Observability Design

Design operational signals — SLIs, SLOs, dashboards, alerts, runbooks — so the system stays understandable under load.

Process

1. Identify critical user journeys

• What must always work? (login, checkout, search, data retrieval, payment).
• For each journey: what is the user-facing outcome?