Description
Define SLOs (availability, p95 latency, payout success) and track error-budget burn weekly. Emit a report and gate deploys when burn-rate exceeds 2x for the previous window.
Requirements and context
- Must be secure, tested, and documented
- Should be efficient and easy to review
- Relevant code:
src/lib/metrics.ts, docs/
- Report must be queryable per service line
Suggested execution
- Fork the repo and create a branch
git checkout -b obs/slo-error-budget
- Implement changes
- Define SLO YAML and parser
- Compute burn-rate from metrics history
- Add weekly cron emitting markdown report
- Validate security and correctness assumptions
Test and commit
- Run tests
- Cover edge cases
- Gap in metrics, partial week, threshold rounding
- Include test output and notes
Example commit message
obs: SLO error-budget burn-rate tracking
Guidelines
- Minimum 95 percent test coverage
- Clear documentation
- Timeframe: 96 hours
Description
Define SLOs (availability, p95 latency, payout success) and track error-budget burn weekly. Emit a report and gate deploys when burn-rate exceeds 2x for the previous window.
Requirements and context
src/lib/metrics.ts,docs/Suggested execution
git checkout -b obs/slo-error-budgetTest and commit
npm testExample commit message
obs: SLO error-budget burn-rate trackingGuidelines