Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Instrument a running service end to end: structured logs, request metrics (latency, error rate, throughput), and traces across at least one service boundary, shipped to a stack you stand up (Prometheus/Grafana/Loki or hosted). Define one SLO with an error budget, wire an alert that fires when the budget burns, and trigger it on purpose to prove it pages.
Logs, metrics, and traces present and correlated; you can answer 'why was this request slow?'
A real SLO with an error budget; an alert fires on burn and was demonstrably triggered.
A dashboard a stranger can read to judge service health at a glance.
Metric labels bounded; you note what the stack costs to run.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Observability stack with SLOs and alerting ## Goal Instrument a running service end to end: structured logs, request metrics (latency, error rate, throughput), and traces across at least one service boundary, shipped to a stack you stand up (Prometheus/Grafana/Loki or hosted). Define one SLO with an error budget, wire an alert that fires when the budget burns, and trigger it on purpose to prove it pages. ## Acceptance criteria - [ ] Signal coverage: Logs, metrics, and traces present and correlated; you can answer 'why was this request slow?' - [ ] SLO & alerting: A real SLO with an error budget; an alert fires on burn and was demonstrably triggered. - [ ] Dashboards: A dashboard a stranger can read to judge service health at a glance. - [ ] Cost/cardinality awareness: Metric labels bounded; you note what the stack costs to run. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.