Monitoring & Observability Interview Questions
Real scenario-based questions, a free monitoring guide, and practice exercises — free to get started.
Free monitoring interview questions
A free sample — one beginner, one intermediate, one advanced — with the full answer shown below each question.
AdvancedWhat's the difference between an SLI, an SLO, and an SLA?
An SLI is the measured metric itself (e.g., 99.95% of requests succeeded). An SLO is the internal target for that metric (e.g., "we aim for 99.9% success"). An SLA is the external, often contractual, commitment tied to consequences if missed. SLOs are usually stricter than SLAs, giving a buffer before a breach becomes a real problem.
IntermediateWhat's the difference between a push-based and pull-based metrics collection model, and which does Prometheus use?
Push-based means the application actively sends metrics to a collector (like StatsD). Pull-based means the collector periodically scrapes metrics from an endpoint the application exposes — Prometheus uses pull, scraping a /metrics endpoint on each target on a schedule, which also makes it easy to detect a target that's down (scrape fails) without separate dead-man's-switch logic.
BeginnerAn alert fires correctly, but the on-call engineer has no idea what to do next. What's missing from the alerting setup?
A linked runbook — the alert itself should point directly to documented steps for diagnosing and responding to that specific condition, rather than leaving the responder to figure out the right response from scratch at 3am under pressure, which is exactly when clear guidance matters most.
Learn monitoring & observability, free to start
A guide covering the three pillars (metrics, logs, traces) and real alerting design — knowing something broke before a customer has to tell you. The first page is free for everyone.
See the full monitoring guide →Practice monitoring for real, no production system needed
Fix a Prometheus CPU alert that flaps and averages away a hot server — adding avg by (instance), a for: duration, and an annotation naming the instance — all graded on real alert-rule correctness.
Monitoring & observability interview FAQ
What are the most commonly asked monitoring and observability interview questions?
Interviewers usually describe a Prometheus alert that flaps or a metric that averages away a real hot server — and ask how you'd fix the rule itself (avg by instance, a for: duration, the right annotation) rather than asking you to define metrics vs logs from memory.
What's the difference between monitoring and observability?
Monitoring tells you something is wrong (a dashboard, an alert). Observability gives you the ability to ask arbitrary new questions about a system you didn't predict in advance — usually through the combination of metrics, logs, and traces together, not just a fixed set of dashboards.
Do I need to know a specific tool like Prometheus or Grafana?
Knowing one real stack well (Prometheus + Grafana is the most common open-source pairing) is enough to demonstrate the underlying concepts — alert rules, the four golden signals, log aggregation — even if the job uses a different commercial tool like Datadog or New Relic.
How do I practice monitoring without a real production system?
Work through fix-the-alert exercises and simulated-terminal incidents first — fixing a flapping CPU alert, reading real metric and log output — all graded on real monitoring concepts, with no production system required.
Starting from zero? Read the step-by-step DevOps career roadmap →
The rest of the guide is waiting.
Create a free account to track your progress through the guide, pass the end-of-page quizzes, and take a full-length readiness check.