Break a freshness SLO into stage-level budgets and identify the bottleneck before alerting.
Support needs customer_health_daily ready by 8:30 a.m. Current completion ranges from 8:12 to 8:51, so the team cannot tell whether source extraction, transformation, validation, or dashboard publish is responsible. Backward freshness budgeting: consumer deadline -> publish -> validation -> transform -> source -> buffer Treating total DAG duration as the only metric means the team discovers the miss after the consumer already needed the data. Start with the consumer moment Health dashboard must be usable by 8:30 a.m. That is the SLO boundary, not the DAG end time. SRE-style SLOs start with user-visible behavior. Here, the user-visible behavior is dashboard…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in