基础设施 4.0 · 优秀 2026-08-12 · 文章

OTel Isn't Going Well (And I Made A Spreadsheet About It)

用 24 个月的 Git 贡献者分布对比 Envoy / Prometheus,把OTel 进度慢从感觉变成证据;对正在评估迁回 vendor SDK 的工程团队有直接参考价值作者画出 PHP / Ruby SDK 维护者高度集中在 2 人Go / .NET 健康度接近 Envoy 的对比图,并把 OTEP Spec Semantic Conventions 各语言 SDK 的锁死链拆给读者看,问题不在人少,而在binary stability gate + 极大 scope + 极少 maintainer三件套共振

打开原文回到归档

OTel Isn't Going Well (And I Made A Spreadsheet About It)

中文摘要

用 24 个月的 Git 贡献者分布对比 Envoy / Prometheus,把OTel 进度慢从感觉变成证据;对正在评估迁回 vendor SDK 的工程团队有直接参考价值作者画出 PHP / Ruby SDK 维护者高度集中在 2 人Go / .NET 健康度接近 Envoy 的对比图,并把 OTEP Spec Semantic Conventions 各语言 SDK 的锁死链拆给读者看,问题不在人少,而在binary stability gate + 极大 scope + 极少 maintainer三件套共振

English Summary

Mat Duggan trades intuition for evidence by plotting 24 months of Git contributor distributions against Envoy and Prometheus. The resulting spreadsheet shows PHP/Ruby SDK maintainers clustered on 2 people and Go/.NET at Envoy-like health, then walks through the OTEP -> Spec -> Semantic Conventions -> per-language SDK locking chain. The diagnosis isn't 'not enough people' but the resonance of three forces: binary stability gates, enormous scope, and very few maintainers.

来源 / Obsidian 引用

  • 本机 Obsidian 同日 digest 落地(ClawFeed 24h / AK-RSS-Digest 89 源 / X-Hot-Brief / 内容选题编排)
  • 评分依据:原文正文(不靠标题/摘要/源声誉)