Create your own Lambda Layer in each OTel language using this starter code. Add the Lambda Layer to your Lambda Function to get tracing with OpenTelemetry.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 70%
Response Time: 6h
First Timer Success: 67%
open-telemetry/opentelemetry-lambda has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-telemetry/opentelemetry-lambda respond to incoming external pull requests in approximately 5.7 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 59.5 places open-telemetry/opentelemetry-lambda in the A tier.
The external contributor pull request merge rate for open-telemetry/opentelemetry-lambda is 70.2%, based on public PR activity from non-core contributors.
open-telemetry/opentelemetry-lambda currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in open-telemetry/opentelemetry-lambda. Prompt code reviews with positive guidance for new contributors.
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-lambda?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 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (88% approval). Large PRs (>500 lines) take ~27 hours (32% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. When using the ruby layer on arm lambda function, the lambda function will fail during the init phase. This is due to the build script not passing a --platform flag to the docker commands, and our release workflow running on x86_64. So every gem that is installed during this build process will be compiled for the x86_64 arch. For example the opentelemetry-exporter-otlp gem that is required, depends on google-protobuf. google-protobuf has some platform-specific precompiled binaries. The same is true for multiple other gems that are required transitively through opentelemetry-instrumentation-all. Describe the solution you'd like Build and release the layer for both x86_64 and arm architectures. Similarly to how it is already being done for the collector layer. Re-visit the integration tests we have since #2322 as currently the ruby integration tests will always fail for the arm arch. Tip: React with 👍 to help prioritize th
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-lambda, 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-lambda acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.2% were successfully merged into the primary branch.
open-telemetry/opentelemetry-lambda has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 hours. 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 59.5 places open-telemetry/opentelemetry-lambda in the Welcoming tier.
The external pull request merge rate is 70.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, open-telemetry/opentelemetry-lambda currently has 1 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-lambda 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.