OpenTelemetry Ruby API & SDK, and related gems
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 50%
Response Time: -
First Timer Success: 63%
open-telemetry/opentelemetry-ruby has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-telemetry/opentelemetry-ruby respond to incoming external pull requests in approximately 0.0 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 62.4 places open-telemetry/opentelemetry-ruby in the A tier.
The external contributor pull request merge rate for open-telemetry/opentelemetry-ruby is 50.0%, based on public PR activity from non-core contributors.
open-telemetry/opentelemetry-ruby currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in open-telemetry/opentelemetry-ruby. Prompt code reviews with positive guidance for new contributors.
Discussions in open-telemetry/opentelemetry-ruby focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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-ruby?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 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (62% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Spec requirement The stdout exporter SHOULD pair with a periodic exporting MetricReader using a default exportIntervalMilliseconds of 10000 for this exporter specifically (sdk_exporters/stdout.md:40-46). Current behavior configurator_patch.rb:37 (permalink) wires ConsoleMetricPullExporter into a PeriodicMetricReader.new(exporter: ...) correctly, but PeriodicMetricReader's interval defaults to OTEL_METRIC_EXPORT_INTERVAL/60000 (export/periodic_metric_reader.rb:25 (permalink)), the general default — nothing special-cases the console exporter's interval to 10000ms. Suggested fix When wiring the console exporter's default PeriodicMetricReader in configurator_patch.rb, pass export_interval_millis: 10_000 explicitly rather than relying on the general-purpose default. Related rows in SPEC_COMPLIANCE_METRICS.md STDOUT-3
Spec requirement The OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION env var (explicit_bucket_histogram/base2_exponential_bucket_histogram, default explicit_bucket_histogram) SHOULD be supported (sdk_exporters/otlp.md:43-70). Current behavior The default (ExplicitBucketHistogram, instrument/histogram.rb (permalink) default aggregation) is correct, but the env var itself is never read in exporter/otlp-metrics or metrics_sdk. A user can't switch the default to exponential histograms via configuration, only by explicitly registering a View. Suggested fix Read OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION in the OTLP exporter or metrics_sdk configurator, and use it to select the default histogram aggregation when no View overrides it. Related rows in SPEC_COMPLIANCE_METRICS.md OTLP-3
Spec requirement Instrument names are case-insensitive; a second registration differing only by case MUST reuse the first-seen name and log a message (sdk.md:1017-1031). Current behavior @instrument_registry is a plain Ruby Hash keyed by the literal (case-sensitive) name string (meter.rb:32,258-260 (permalink)), so create_counter("requestCount") followed by create_counter("RequestCount") registers two independent instruments instead of being detected as the same name under case-insensitive comparison. Suggested fix Normalize the registry key (e.g. downcase) when checking for an existing instrument, while preserving and reusing the first-seen name's original casing, and log a message on the case-differing collision. Related rows in SPEC_COMPLIANCE_METRICS.md SDK-37
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-ruby, 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-ruby acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
open-telemetry/opentelemetry-ruby has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 62.4 places open-telemetry/opentelemetry-ruby in the Welcoming tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, open-telemetry/opentelemetry-ruby 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-ruby 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.