Monitoring, Logging, and Observability Questions

Understanding running systems through their signals. Covers metrics, logs, and traces, instrumentation, dashboards, alerting design, and log analysis and correlation for debugging production. Emphasizes designing observability so problems are detectable and diagnosable before users are affected.

HardSystem Design
76 practiced

Design an automated system that reacts to error-budget burn: it should be able to roll back a feature flag, shift traffic away from a bad region, or freeze deploys entirely, depending on how fast the budget is burning. What safety checks and manual overrides would you build in, and how would you test it without risking a bad automated rollback in production?

HardTechnical
45 practiced

During a cascading failure, dozens of related alerts can fire within minutes across services and regions. How would you make sure on-call sees a clear signal instead of a flood, without losing the context you need to find the actual root cause?

MediumTechnical
54 practiced

How would you set a naming and labeling convention for metrics across a multi-team organization, so ownership is discoverable and cardinality stays under control?

MediumTechnical
51 practiced

Have you managed your dashboards, alert rules, and metric definitions as code, checked into version control the same way as application code? What does that actually buy you, and what's harder about it compared to clicking around in a UI?

MediumTechnical
55 practiced

Walk me through instrumenting a request handler for an API endpoint. At each stage, say authentication, the business logic, and the database call, what would you measure, and which metric type would you use for it?

Unlock Full Question Bank

Get access to all Monitoring, Logging, and Observability interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.