OTel isn’t going well(matduggan.com)
229 points by hn_acker 1 day ago | 117 comments
tl;dr: OpenTelemetry's slow progress stems from a three-way collision: strict stability guarantees, a huge scope across many languages/frameworks, and too few maintainers—with data showing several SDKs (PHP, Ruby, C++, Kotlin) dangerously dependent on 1-2 people, far worse than comparable CNCF projects like Envoy or Prometheus. The author proposes a time-bound "beta" tier to get real user feedback without permanent lock-in, honest labeling of maintenance tiers across languages, and more public acknowledgment that the project urgently needs more (ideally vendor-independent) maintainers.
HN Discussion:
  • SDKs are overly complex, stateful, and Java-centric, failing modern architectures
  • ~Tracing, metrics, and logs should be unified rather than designed separately
  • OTel's vendor-neutral exporter model is too complex; a self-hostable end-to-end solution is needed
  • Vendor support and performance overhead remain frustratingly poor across the ecosystem
  • Instrumentation effort is worthwhile and observability deserves more evangelism