What is the difference between monitoring and observability in practice? [Basic]
Answer
In practice, monitoring answers known questions like 'is the service up?', while observability helps answer unknown questions like 'why is only one tenant seeing latency after this deployment?'. Monitoring is alerting and visibility; observability is investigation capability.
Technical explanation
A monitoring-only setup often has many infrastructure alerts but weak request context, so incidents require guessing.
An observable system includes service-level signals, consistent labels, trace propagation, structured logs, deployment markers, and ownership metadata.
The practical test is whether an on-call engineer can debug a novel production issue without adding code or waiting for another deployment.
Hands-on example
Hands-on checklist: trigger a test failure, then try to answer: affected endpoint, affected version, affected region, customer impact, slow dependency, deploy correlation, and error class. If the telemetry cannot answer these, the system is monitored but not truly observable.
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 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]
- How do you set an SLO target, and why not just aim for 100%? [Basic]