Observability for DevOps Engineers
In DevOps, observability is the ability to understand what a system is doing from the data it emits. Metrics show numeric trends, logs record events and traces follow a request through services. Tools such as Prometheus, Grafana, Loki and OpenTelemetry collect and display them, and alerting with on-call rotations turns signals into timely human action.
Stage: Observability and Reliability · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Observability
- Instrument an app with a Prometheus counter and histogram
- Write a PromQL query for request rate and error ratio
- Build a Grafana dashboard for the four golden signals
- Add distributed tracing with OpenTelemetry
- Write alerts that signal user impact rather than every blip
- Set up on-call routing and runbooks for alerts
Observability interview questions
What is the difference between monitoring and observability?
Monitoring checks known conditions with predefined dashboards and alerts. Observability lets you ask new questions about unknown problems by exploring rich metrics, logs and traces. It builds on monitoring but supports debugging of unexpected failures.
What are the four golden signals?
Latency, traffic, errors and saturation. They come from Google's SRE book and give a compact view of service health: how long requests take, how much demand there is, how many requests fail and how full the resources are.
Where Observability fits in the DevOps Engineer roadmap
Observability belongs to the Observability and Reliability stage (advanced level), which takes about 1 hours. Know what is happening and respond well.
Other units in this stage
Back to the full DevOps Engineer roadmap