Observability in 2026: OpenTelemetry, Distributed Tracing, and the Three Pillars

Observability in 2026: OpenTelemetry, Distributed Tracing, and the Three Pillars Quietly, OpenTelemetry won. The fights now happen over sampling, cardinality, and whether your Collector falls over at 2 a.m. Community take: what people actually complain about I keep seeing the same threads in Discord and GitHub issues. Folks love vendor-neutral OTLP, then they hit reality. Traces drop under load, metrics explode from one "helpful" label, and somebody asks why the Collector needs so much memory for tail sampling. On the Kubernetes side, the consensus seems to be: most teams are upgrading their OTel setup, but they are doing it in slices. As one SRE put it in a Slack thread, "I'll take boring metrics with clean ownership over 100% traces I cannot afford." I agree, even if it feels less cool. Tail sampling scares people: buffering whole traces feels risky, especially when traffic spikes and the incident commander asks you to "turn up tracing." I have watched teams do that and then OOM the