Alerting that people trust
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
write alerts that are actionable.
Planned topics
- Alert on symptoms users feel (error rate, latency), not on causes (CPU at 80%).
- Every alert needs: what is wrong, impact, first steps, runbook link.
- Use
for:durations to avoid flapping; route by severity (page versus ticket). - Group and deduplicate in Alertmanager so one fault gives one alert.
- Review noisy alerts regularly; delete or fix them.
Draft outline details
Demonstration
- alert: CheckoutHighErrorRate
expr: checkout_error_ratio > 0.02
for: 5m
annotations: { runbook_url: "https://wiki.example/runbooks/checkout-errors" }Check your understanding
Why not alert on CPU?
Show answer
High CPU may harm nobody; users feel errors and latency.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.