OpenTelemetry, a vendor‑agnostic observability framework, faces challenges with maintainer scarcity and slow feature adoption, according to an analysis of project activity over 24 months. The project splits its code base into core components maintained directly by the OpenTelemetry community and contribution‑based modules contributed by vendors and the wider community. Many language SDKs and instrumentations reside in the contribution layer, which can increase complexity for users. The analysis examined pull request metrics for several SDKs, including opentelemetry-go, opentelemetry-dotnet, and others, finding that a small number of individual maintainers handle a large share of merges. Projects such as prometheus and envoy show broader distribution of contributors. In OpenTelemetry, language SDKs like opentelemetry-ruby and opentelemetry-php have limited merge activity, indicating concentration of effort. Slow movement of enhancements through the specification process and the requirement for additional approvals under a public‑API review step have extended development cycles. A proposed solution suggests introducing a time‑bound beta tier to give experimental features longer, more accessible exposure before final stabilization. The author also notes that the project’s heavy reliance on a few maintainers employed by sponsoring companies creates a conflict of interest and limits community participation. The findings highlight a need for increased staffing and clearer stability commitments to sustain OpenTelemetry’s growth and broader adoption.