Kubernetes and Cloud Native Associate (KCNA)Cloud Native ObservabilityMedium
A platform engineering team is implementing a system to monitor the health and performance of their Kubernetes cluster. They need a solution that can periodically execute predefined checks against their services and emit metrics indicating their availability and response times. Which type of monitoring is best suited for this requirement?
- ABlack-box monitoring
- BWhite-box monitoring
- CDistributed tracing
- DApplication logging
Show answer & explanationAnswer & explanation
Correct answer: A. Black-box monitoring
Black-box monitoring involves observing a system from the outside, typically by making requests to its external interfaces and measuring its responses, without internal knowledge of its components. This aligns with executing predefined checks against services to determine availability and response times. White-box monitoring, in contrast, uses internal metrics.
Why the other options are wrong
- B. White-box monitoring uses internal system metrics and instrumentation, not external checks.
- C. Distributed tracing tracks requests across services, focusing on latency and causality, not periodic health checks.
- D. Application logging records events within an application, but doesn't actively perform checks on service health.
Black-box Monitoring
Observing a system's behavior from an external perspective, typically by interacting with its public interfaces and measuring its responses, without insight into its internal workings.
- Focuses on user experience and external availability.
- Often involves synthetic transactions or API calls.
- Complements white-box monitoring by verifying end-to-end functionality.
Memory trick: Is the box black (external) or white (internal)?