OpenTelemetry: trace, log, metric — one stack, three signals
What it actually costs to consolidate observability onto OTel + Grafana + Loki + Tempo + VictoriaMetrics, and what you get back.
// distributed systems
OTel + Grafana stack
trace / log / metric on one backbone
Stub. Full post body to follow.
The three observability signals — traces, logs, metrics — have historically lived in different vendors with different query languages, different sampling philosophies, and different costs. The OTel stack lets one ingest pipeline feed all three, and Grafana’s dashboards can correlate across them with TraceID-as-foreign-key. The migration is non-trivial; the steady state pays for itself the first time someone debugs a production incident at 2 a.m.
// RELATED
2026-03-20 · 11 min · DISTRIBUTED SYSTEMS
Building a CDC pipeline with Debezium — without breaking the source
Lessons from tailing a multi-tenant Mongo oplog into Kafka without putting the source database under more load than it already had.
2026-03-05 · 8 min · DISTRIBUTED SYSTEMS
Normalizing GPS telemetry from 8k vehicles across half a dozen sources
Polished APIs, flaky devices, customer-internal feeds — what cross-source GPS normalization actually looks like in production.