Bird
0
0

You want to design an alerting strategy that avoids alert storms caused by multiple microservices failing simultaneously. Which approach is best?

hard📝 Trade-off Q8 of 15
Microservices - Monitoring and Observability
You want to design an alerting strategy that avoids alert storms caused by multiple microservices failing simultaneously. Which approach is best?
AImplement alert aggregation to group related alerts
BSend alerts immediately for every failure without grouping
CDisable alerts during peak traffic hours
DIncrease alert thresholds to very high values
Step-by-Step Solution
Solution:
  1. Step 1: Understand alert storms and their cause

    Alert storms happen when many alerts fire at once, overwhelming responders.
  2. Step 2: Identify strategy to reduce alert noise

    Alert aggregation groups related alerts into one, reducing noise and improving clarity.
  3. Final Answer:

    Implement alert aggregation to group related alerts -> Option A
  4. Quick Check:

    Alert storm solution = Aggregation [OK]
Quick Trick: Aggregate alerts to prevent alert storms [OK]
Common Mistakes:
MISTAKES
  • Sending all alerts immediately causing noise
  • Disabling alerts risking missed issues
  • Raising thresholds hiding real problems

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes