eBPF-based autoinstrumentation of web applications and network metrics
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 90%
Response Time: 7d
First Timer Success: 100%
grafana/beyla has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in grafana/beyla respond to incoming external pull requests in approximately 172.4 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 71.5 places grafana/beyla in the S tier.
The external contributor pull request merge rate for grafana/beyla is 90.1%, based on public PR activity from non-core contributors.
grafana/beyla currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in grafana/beyla. 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/grafana/beyla?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~112 hours (96% approval). Large PRs (>500 lines) take ~828 hours (41% approval). Keep your diff compact for rapid review.
Beyla's trace attribute selector controls error and network attributes as well as payload attributes. Fields to document attributes.select.traces.include attributes.select.traces.exclude Add these accepted attribute values and document their default inclusion: error.type network.peer.address network.peer.port network.protocol.version Explain when each attribute is available and include a focused exclusion example. Update the default-attribute table and its accompanying explanation.
Beyla lets users add attributes to the application metric group and explicitly select service identity as metric-level attributes. Fields to document attributes.extra_group_attributes.app attributes.select.<metric>.include attributes.select.<metric>.exclude Document app as an accepted extra-group key alongside k8s_app_meta, its list-of-attribute-names format, and the metrics to which it applies. Explain that service.name and service.namespace are available as resource attributes and are opt-in as application metric-level attributes. Document their underscore spellings and show examples using the app group and a metric selector.
Beyla lets users select database namespace and response-status attributes on database client and server operation metrics. Fields to document attributes.select.db_client_operation_duration.include attributes.select.db_client_operation_duration.exclude attributes.select.db_server_operation_duration.include attributes.select.db_server_operation_duration.exclude Document the accepted values db.namespace and db.response.status_code, including the Prometheus-style spellings db_namespace and db_response_status_code. Explain their default inclusion, protocol-dependent availability, and cardinality implications. Include an exclusion example covering both metric selectors.
Beyla can capture spans created through the Node.js OpenTelemetry API using an injected span bridge. Fields to document nodejs.manual_spans / BEYLA_NODEJS_MANUAL_SPANS nodejs.enabled / BEYLA_NODEJS_ENABLED Document the boolean defaults: manual-span capture is disabled and agent injection is enabled. Explain the injection prerequisite, capture when no OpenTelemetry SDK is registered, and behavior when an SDK registers. Include a minimal YAML example.
Beyla's application_runtime feature enables runtime metrics for Go, Java, Node.js, and Python. Language-agent settings control collection that depends on injected agents. Fields to document metrics.features discovery.instrument[].metrics.features otel_metrics_export.features prometheus_export.features nodejs.enabled / BEYLA_NODEJS_ENABLED javaagent.enabled / BEYLA_JAVAAGENT_ENABLED jvm_runtime_metrics.sampling_interval / OBI_JVM_RUNTIME_METRICS_SAMPLING_INTERVAL metrics.buckets.v8js_gc_duration_histogram otel_metrics_export.buckets.v8js_gc_duration_histogram prometheus_export.buckets.v8js_gc_duration_histogram Document application_runtime coverage with global and per-service examples. Explain that disabling the Node.js agent disables its runtime metrics. Disabling the Java agent disables class, thread, and CPU metrics while HotSpot memory metrics remain available. Document the JVM sampling interval's 1s default and its effect on HotSpot memory sampling and agent-backed snapshots. Doc
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 grafana/beyla, 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 grafana/beyla acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.1% were successfully merged into the primary branch.
grafana/beyla has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 71.5 places grafana/beyla in the Elite tier.
The external pull request merge rate is 90.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, grafana/beyla currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for grafana/beyla 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.