#slo

4 notes across 2 topics

# Observability

1 — Dashboard Design

The three-question test for a vanity panel, why the same underlying data needs a different dashboard for different audiences, and the top-down layout that mirrors how an investigation actually drills down.

observability slo alerting incident-response book

Jul 17, 2026

1 — Alerting & Alert Routing

Symptom-based vs. cause-based alerting, the noise-reduction problem (dedup, grouping, correlation), and routing/escalation — the design discipline standing between a real page and a bad one.

observability slo alerting incident-response book

Jul 17, 2026

2 — SLOs & Error Budgets

SLI/SLO/SLA, the error budget as a spendable resource rather than a compliance number, burn rate as the mechanism connecting the two, and why multi-window multi-burn-rate alerting exists at all.

observability slo alerting incident-response book

Jul 17, 2026

# System Design

All System Design notes →

4. Observability of the Pipeline Itself

What to instrument at every layer of the telemetry ingestion pipeline, the pipeline's own SLOs, distributed tracing of the pipeline itself, and the synthetic canary that catches stalls no component metric surfaces.

system-design observability telemetry maang-prep slo

← All notes