Prompt
I hate that logs metrics and traces live in separate tools
Latest observation
Oct 5, 2026
OpenAI APIWeb search: off
Totally fair — that split is one of the biggest sources of friction in observability.
What usually hurts:
- Context switching between tools just to answer one incident
- Broken correlation when logs, metrics, and traces don’t share the same IDs
- Slow debugging because you can’t go from “alert” → “trace” → “log line” quickly
- Duplicated setup and cost across multiple vendors
A lot of teams want a single workflow where they can:
- see an alert from a metric,
- jump to the trace for the affected request,
- open the relevant logs for that exact span/service,
- and do all of that with shared labels/attributes.
There are a few common ways people handle it:
- One platform for all three signals: simplest UX, fewer moving parts
- Best-of-breed tools with strong correlation: more flexible, but integration work
- OpenTelemetry everywhere: helps unify instrumentation and make cross-linking easier, even if storage remains separate
If you want, I can help you think through:
- how to unify them in your current stack,
- what architecture reduces tool-switching the most,
- or how to pitch a “single pane of glass” observability setup internally.