What is the difference between black-box and white-box monitoring? [Intermediate]
Answer
Black-box monitoring tests behavior from the outside, like a user or dependency would see it. White-box monitoring uses internal metrics from the system itself. Both are needed: black-box confirms external experience; white-box explains internal causes.
Technical explanation
Black-box checks catch DNS, TLS, routing, load balancer, and end-to-end failures that internal metrics may miss.
White-box metrics show service internals, resource saturation, dependency errors, and code-level behavior.
For paging, black-box or SLO symptom checks are often stronger than infrastructure-only white-box alerts.
Hands-on example
Example: use blackbox_exporter to probe https://app.example.com/health from multiple regions. Use white-box Prometheus metrics to monitor checkout request duration, dependency error rate, and queue depth. If black-box fails but service metrics look fine, check DNS, ingress, CDN, and TLS.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Observability interview questions
- What is observability, and how is it different from traditional monitoring? [Basic]
- What are the three pillars of observability (metrics, logs, traces)? [Basic]
- What is the difference between monitoring and observability in practice? [Basic]
- What are the four golden signals of monitoring? [Basic]
- What is the difference between the USE method and the RED method? [Basic]
- When would you use the USE method versus the RED method? [Basic]
- What is an SLI, an SLO, and an SLA, and how do they relate? [Basic]
- How do you choose good SLIs for a service? [Basic]