Skip to content
RED SAGSkills
easyDevOps Engineer interview question

What is the difference between monitoring and observability, and what are the main signals you would collect for a web service?

What the interviewer wants to hear

  • Monitoring checks known failure modes with dashboards and alerts
  • Observability lets you ask new questions about unknown problems
  • Metrics, logs and traces as core signals
  • Golden signals: latency, traffic, errors, saturation
  • Correlation through shared IDs and labels

Model answer

Monitoring is watching for problems you already know about: you define dashboards and alerts for things like error rate or disk space. Observability is a property of the system: how well you can understand its internal state from the data it emits, including problems you never predicted. In practice you need both. For a web service I would collect metrics for the four golden signals: latency, traffic, errors and saturation, mostly with Prometheus. I would ship structured logs with request IDs to a central store, and add distributed traces with OpenTelemetry so I can follow one request across services. The key is correlation: the same service, version and trace ID labels on all three signals, so I can jump from an alert on a metric to example traces and then to the logs for exactly those requests.

Can you answer it under time pressure?

Take a timed easy round and get scored on every answer.

Start mock interview

More easy DevOps Engineer questions