Observability: Metrics Logs Traces
As a Architect engineer, explain Observability: Metrics Logs Traces. What problem does it solve and how would you describe it in an interview?
Answers use simple, clear English.
Quick interview answer
At Architect depth: start with the problem, then mechanism, then a short example. Metrics for SLIs/SLOs, structured logs, distributed traces.
Detailed answer
At Architect depth: start with the problem, then mechanism, then a short example. Metrics for SLIs/SLOs, structured logs, distributed traces. Correlate with TraceId. Alert on symptoms (latency/errors) not only CPU. Core: Metrics for SLIs/SLOs, structured logs, distributed traces. Correlate with TraceId. Alert on symptoms (latency/errors) not only CPU. Real-time example: p99 latency burn alert → trace shows slow DB span → log shows lock wait. Pros: Faster incident diagnosis. Cons: Cost/cardinality explosions. Common mistakes: Paging on raw CPU; no runbooks. Best practices: SLO-based alerts; sampling; exemplars linking metrics→traces. Audience level: Architect.
Full explanation
Metrics for SLIs/SLOs, structured logs, distributed traces. Correlate with TraceId. Alert on symptoms (latency/errors) not only CPU.
Real example & use case
p99 latency burn alert → trace shows slow DB span → log shows lock wait.
Pros & cons
Pros: Faster incident diagnosis. Cons: Cost/cardinality explosions.
Common mistakes
Paging on raw CPU; no runbooks.
Best practices
SLO-based alerts; sampling; exemplars linking metrics→traces.
Follow-up questions
- How would you test Observability: Metrics Logs Traces?
- What metrics prove Observability: Metrics Logs Traces is healthy in prod?
- How does Observability: Metrics Logs Traces change at 10× traffic?