Kubernetes and Cloud Native Associate (KCNA)Cloud Native ObservabilityMedium
A client is running a mission-critical financial application on Kubernetes. They require an observability strategy that ensures an immediate response to any deviation from normal behavior, even subtle ones, to prevent service disruptions. This necessitates defining clear thresholds for key metrics and automatically notifying responsible teams when these thresholds are breached. Which observability practice is being described?
- AForecasting
- BRoot cause analysis
- CAlerting
- DCapacity planning
Show answer & explanationAnswer & explanation
Correct answer: C. Alerting
The scenario explicitly describes defining thresholds for metrics and automatically notifying teams upon breaches, which is the core function of alerting. Alerting is designed to provide immediate notification of issues, enabling rapid response to prevent service disruptions. Capacity planning, forecasting, and root cause analysis are related but distinct practices.
Why the other options are wrong
- A. Forecasting predicts future trends, not real-time detection of deviations.
- B. Root cause analysis is performed *after* an incident to understand why it happened, not to detect it in real-time.
- D. Capacity planning involves estimating future resource needs, not immediate issue notification.
Alerting
The process of detecting anomalous or undesirable conditions in a system, typically by monitoring metrics or logs against predefined thresholds, and notifying relevant personnel or automated systems.
- Aims for timely detection of issues.
- Often integrates with communication tools (e.g., PagerDuty, Slack).
- Requires carefully defined thresholds to avoid alert fatigue.
Memory trick: Observe, then Alert, to keep things stable.