Question presented to candidate:
"People talk about the three pillars of observability. What are they, what is each one good and bad at, and how would you use them together when checkout starts failing in production?"
What a strong answer should cover:
Metrics: cheap numeric time series aggregated over labels; best for dashboards and alerting, weak at explaining one request; label cardinality limits the detail they can carry
Logs: timestamped event records, ideally structured (key=value or JSON); best for the why of one event; expensive in volume, so levels, sampling and retention matter
Traces: one request across services as a tree of spans sharing a trace ID; best for where time or errors happen; usually sampled
Correlation is the point: the same trace ID in spans and logs, exemplars from metric buckets to traces, shared resource attributes (service, version) so you can pivot from an alert to a trace to its logs
Monitoring vs observability: known questions vs new questions without shipping new code; OpenTelemetry as the vendor-neutral way to produce all three
Beyond the pillars: continuous profiles (an OpenTelemetry signal in Alpha since March 2026), wide structured events, and SLOs as the thing the signals serve
Code / implementation expected: Optional โ explaining a real investigation flow matters more; the example walks one simulated incident through all three signals.
observability
2
Try it yourself
Sketch your approach before you read the solution. That is what the interview tests.
Stuck? Get a hint.
A short nudge toward the approach. It will not give the answer away.
3
Solution
Target Audience: Beginners who have seen a dashboard or grepped a log file and want to understand what observability means, and candidates who need crisp vocabulary for an interview.
Difficulty: Medium
Verified with: Node 22.22 and Python 3.12 (both print identical output). The history of the "three pillars" phrase is from CrowdStrike's "Observability (Re)defined" article; the profiles signal status from the OpenTelemetry documentation and ClickHouse's write-up of the Alpha announcement.
How to read this doc: Every idea is explained in plain language first, then tagged with ๐ Interview term: so you also learn the words an interviewer expects. Every number comes from running the example; the Verified section quotes its full output.
1. Why This Even Matters โ A Story First
You are driving and a red warning light comes on. That light is a metric: one numbe
The solution is hidden so you can try first
16 min read ยท 12 sections
4
Read the code
One incident through all three pillars: a metric alert, a trace waterfall, the matching logs, and the cost of each signal