OpenTelemetry Collector
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 49%
Response Time: 2d
First Timer Success: 34%
open-telemetry/opentelemetry-collector has a recorded first-timer success rate of 34.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-telemetry/opentelemetry-collector respond to incoming external pull requests in approximately 38.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.8 places open-telemetry/opentelemetry-collector in the A tier.
The external contributor pull request merge rate for open-telemetry/opentelemetry-collector is 48.6%, based on public PR activity from non-core contributors.
open-telemetry/opentelemetry-collector currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in open-telemetry/opentelemetry-collector. Maintains strict focus on technical quality and test standards.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/open-telemetry/opentelemetry-collector?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (61% approval). Large PRs (>500 lines) take ~184 hours (22% approval). Keep your diff compact for rapid review.
Component(s) No response Is your feature request related to a problem? Please describe. The Collector's log level is configured globally via service::telemetry::logs::level, which applies uniformly to every component. There is no way to adjust the log verbosity of a single component without affecting all others. This becomes a problem for resource-intensive components like the ebpf-profiler receiver, where enabling debug logging is essential for troubleshooting but doing so at the service level floods the output with noise from every other component in the pipeline. The ebpf-profiler is actively working around this limitation by introducing component-specific configurations like verbose_mode (opentelemetry-ebpf-profiler#1317), but this forces each component to reinvent its own log level control rather than relying on a collector-level mechanism. See opentelemetry-ebpf-profiler#417 for the broader discussion. Describe the solution you'd like Allow users to override the log level for ind
Component(s) No response Describe the issue you're reporting We should ensure, with a CI step, that templates are properly tab-formatted, even before running gofmt in the generated code. Related: #14669 #14688 #14697 Tip React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to open-telemetry/opentelemetry-collector, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of open-telemetry/opentelemetry-collector acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.6% were successfully merged into the primary branch.
open-telemetry/opentelemetry-collector has a recorded first-timer success rate of 34.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.8 places open-telemetry/opentelemetry-collector in the Welcoming tier.
The external pull request merge rate is 48.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, open-telemetry/opentelemetry-collector currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for open-telemetry/opentelemetry-collector are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.