Service level objective#102
Open
gloskull wants to merge 2 commits into
Open
Conversation
Add SLO burn-rate monitoring and runbook
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Description
src/slo.rsthat defines SLO constants,SloTarget,SloWindow,SloEvaluation, and theevaluate_windowandpublish_slo_evaluationhelpers.observed_error_bps,burn_rate_x100) and latency violation logic, and encode alert signals asSloSignal::{Healthy,Ticket,Page}.pub mod slo;tosrc/lib.rsand include a human‑facingSLO_MONITORING_RUNBOOK.mddescribing architecture, alert policy, dashboards, canary checks, and incident response.src/slo.rscovering default targets, healthy state, ticket threshold, page threshold, and latency‑based paging.Testing
cargo test slo --lib, which executed the SLO test suite and reported5 passed; 0 failed.Closes #89