Alerting strategies in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Alert Severity Levels

In a microservices environment, alerts are categorized by severity to prioritize responses. Which of the following best describes the difference between a critical alert and a warning alert?

A A critical alert is for minor issues that can be ignored temporarily, while a warning alert requires immediate action to prevent downtime.

B A critical alert indicates an immediate service outage affecting users, while a warning alert signals a potential issue that does not yet impact service availability.

C A critical alert is only sent during business hours, while a warning alert is sent 24/7.

D A critical alert is generated by automated systems, while a warning alert is manually created by engineers.

💡 Hint

Think about how urgent the problem is and its impact on users.

Critical alerts signal urgent problems that affect users immediately and need fast action. Warning alerts indicate issues that might become serious but currently do not disrupt service.

❓ Architecture

intermediate

Designing an Alert Aggregation System

You want to design an alert system that groups similar alerts from multiple microservices to reduce noise. Which architectural component is essential for this aggregation?

A A caching layer that stores user session data.

B A distributed database that stores raw logs without processing alerts.

C A load balancer that routes user requests to healthy microservices.

D A centralized alert manager that receives alerts and groups them based on service and error type.

💡 Hint

Focus on where alerts are collected and processed before notifying engineers.

A centralized alert manager collects alerts from services and groups similar ones to reduce alert fatigue and improve response efficiency.

❓ scaling

advanced

Scaling Alert Delivery for High Traffic

Your microservices generate thousands of alerts per minute during peak load. Which strategy best ensures alert delivery remains reliable and timely?

A Implement a message queue with backpressure handling between alert producers and notification services.

B Send alerts directly from each microservice to engineers via email without buffering.

C Store all alerts in a database and send notifications once a day in a batch.

D Disable alerts during peak traffic to avoid overwhelming the system.

💡 Hint

Consider how to handle bursts of alerts without losing or delaying them.

A message queue buffers alerts and manages flow control, ensuring no alerts are lost and notifications are timely even under heavy load.

❓ tradeoff

advanced

Tradeoffs in Alert Threshold Settings

Setting alert thresholds too low or too high affects system monitoring. What is the main tradeoff when choosing a very low threshold for alerting?

A Low thresholds reduce alert noise but delay detection of real problems.

B Low thresholds improve system performance by reducing monitoring overhead.

C Low thresholds increase alert noise, causing alert fatigue, but catch issues early.

D Low thresholds prevent any alerts from being sent, ensuring engineers are not disturbed.

💡 Hint

Think about how many alerts engineers receive and how early problems are detected.

Low thresholds trigger many alerts, which can overwhelm engineers, but help detect problems quickly before they worsen.

❓ estimation

expert

Estimating Alert Storage Requirements

Your microservices generate an average of 500 alerts per minute. Each alert record is approximately 1 KB in size. You want to store alerts for 30 days for audit and analysis. How much storage space do you need?

A Approximately 21.6 GB

B Approximately 720 MB

C Approximately 43.2 GB

D Approximately 1.44 TB

💡 Hint

Calculate total alerts per month and multiply by alert size.

500 alerts/min × 60 min/hr × 24 hr/day × 30 days = 21,600,000 alerts. At 1 KB each, total is about 21.6 GB.