Topic lessonTopic: Monitoring and recovering event processing
Calculate an SLO and error budget from completed work
Define a good outcome before setting a service-level objective. Use an image-processing example to calculate how many failures the target allows and how fast that allowance is being consumed.
Choose the denominator, success condition, and observation window for a request-based SLI, then calculate the remaining error budget.
All observations are fictional. This example covers operational objectives, not service agreements or refunds.
Measure the completion the user needs
A request-based SLO measures the fraction of eligible requests that qualify as good. Here an image conversion is good if its result is stored within the agreed deadline after intake.
- User outcome → PopulationChoose the operation
- Population → Success conditionDefine numerator and denominator
- Success condition → ComparisonCompare with the target
- User outcome
- Use the converted image on time
- Population
- Requests accepted during the window
- Success condition
- Result stored within two minutes
- Comparison
- Attainment and remaining allowance
Calculate a 99.5% target for 10,000 requests
| Measure | Count | Interpretation |
|---|---|---|
| Eligible requests | 10,000 | Denominator includes the observed eligible work. |
| Allowed failures at 99.5% | 50 | 10,000 × 0.005. |
| Failures or missed deadlines | 30 | 99.7% attainment, leaving the equivalent of 20 requests. |
The remaining 20 is a calculation for the observed volume. A moving window changes its contents when requests arrive and expire. Compare a short-window failure rate with the allowed rate to track how quickly the budget is being consumed.
Account for blind spots and short-term changes
Separate intake responses from completed work. An acceptance response does not establish that an output was stored. Correlate results with deadlines and decide how to handle gaps in measurement.
Keep burn rate and budget remaining distinct. A short-window failure rate of 1.5% divided by an allowed rate of 0.5% gives a burn rate of 3. Use the longer observation window separately to assess attainment.
Use matching conditions for targets and observations
Choose an option to see the result and explanation.
Check, then explain in your own words
- Define eligible requests, the deadline, and the good outcome.
- Calculate attainment and remaining budget from the denominator and failures.
- Compare short-window burn with long-window budget.
Check your understanding: Can the SLO be missed even when every intake succeeds?
Yes. If it measures on-time storage, too many failed or late outputs can miss the target.
An intake response and the outcome the user needs are separate measurements.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- Service level objectives (SLOs)Checked:
Scope and conditionsRequest-based and period-based SLOs, attainment, error budgets, and burn rate.
Used in this lessonMeasure the completion the user needs Calculate a 99.5% target for 10,000 requests Account for blind spots and short-term changes