It’s 3 a.m. on a Sunday. Your phone goes off. An alert says "payments service: high error rate."
You open the dashboard. The error rate is up. That’s all the dashboard knows. It
doesn’t know which errors, which users, which
dependency, which code path. Eight minutes later you’re still searching
logs with grep, refilling a glass of water, and silently regretting your
career choices.
Now imagine the same alert with a single click that filters every log, metric and trace to only the failing requests, joined by trace ID. The cause — a third-party API timing out for South-American payment cards — is in front of you in 90 seconds. You disable that path with a feature flag and go back to bed.
That second scenario is what observability is for.