This repository contains set of components extending functionality of the OpenTelemetry .NET SDK. Instrumentation libraries, exporters, and other components can find their home here.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 79%
Response Time: -
First Timer Success: 69%
open-telemetry/opentelemetry-dotnet-contrib has a recorded first-timer success rate of 68.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-telemetry/opentelemetry-dotnet-contrib 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 69.5 places open-telemetry/opentelemetry-dotnet-contrib in the A tier.
The external contributor pull request merge rate for open-telemetry/opentelemetry-dotnet-contrib is 79.5%, based on public PR activity from non-core contributors.
open-telemetry/opentelemetry-dotnet-contrib currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in open-telemetry/opentelemetry-dotnet-contrib. Reviews community pull requests with focus on project quality.
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-dotnet-contrib?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (36% approval). Keep your diff compact for rapid review.
Context: open-telemetry/opentelemetry-dotnet#7324 The Geneva InfluxDB and OneCollector exporter uses unsafe for performance reasons: opentelemetry-dotnet-contrib/src/OpenTelemetry.Exporter.Geneva/OpenTelemetry.Exporter.Geneva.csproj Line 6 in bfa4e8f <AllowUnsafeBlocks>true</AllowUnsafeBlocks> The Geneva exporter also uses MemoryMarshal (code search) and Unsafe: opentelemetry-dotnet-contrib/src/OpenTelemetry.Exporter.Geneva/External/LinuxTracepoints-Net/Provider/EventHeaderValue128.cs Line 47 in ac5a824 Unsafe.CopyBlockUnaligned(ref this.Byte0, ref MemoryMarshal.GetReference(source), 16); C# 15 16 in the .NET 11 12 timeframe is looking to make changes to unsafe code to reduce its usage for security reasons, see Unsafe Evolution for further context. To improve th
Currently ASP.NET Core instrumentation library either uses: ASP.NET Core created activity with context propagated via DistributedContextPropagator when TextMapPropagator extracted ActivityContext matches current Activity instrumentation library created activity when TextMapPropagator extracted context doesn't match current Activity We would like to have TextMapPropgator which ignores trace context from incoming request to have new root activity per incoming request. With TextMapPropagator we tried: returning default PropagationContext, but then it will simply use ASP.NET Core created Activity with propagated context because ActivityContext will not be valid: opentelemetry-dotnet-contrib/src/OpenTelemetry.Instrumentation.AspNetCore/Implementation/HttpInListener.cs Line 106 in d08b817 if (ctx.ActivityContext.IsValid() returning PropagationContext with new ActivityContext(A
Component OpenTelemetry.Instrumentation.EntityFrameworkCore Is your feature request related to a problem? The current implementation does not sanitize values in db.query.text or db.statement for NoSQL-like databases. This can lead to sensitive data being captured in telemetry. https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.EntityFrameworkCore/Implementation/EntityFrameworkDiagnosticListener.cs#L186-L189 What is the expected behavior? db.query.text or db.statement should be sanitized consistently, similar to how parameterized SQL queries are handled. Which alternative solutions or features have you considered? Disabling query text collection for NoSQL-like databases 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.
I noticed that various libraries are not adding a schema URL to their ActivitySource and/or Meter instances. Where possible, we should add them: Instrumentation.AspNetCore - #4066 #4373 Instrumentation.AWS - #4063 Instrumentation.AWSLambda - #4063 Instrumentation.Cassandra - #4639 Instrumentation.ConfluentKafka - #4636 Instrumentation.ElasticsearchClient - #4635 Instrumentation.EntityFrameworkCore - #4078 Instrumentation.EventCounters - #4640 Instrumentation.GrpcCore - #4338 Instrumentation.GrpcNetClient - #4338 Instrumentation.Hangfire = #4641 Instrumentation.Http - #4082 Instrumentation.Owin - #4375 Instrumentation.Process - #4088 Instrumentation.Quartz - #4642 Instrumentation.Runtime - #4087 Instrumentation.ServiceFabricRemoting - #5401 Instrumentation.StackExchangeRedis - #4095 Instrumentation.Wcf - #4377
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-dotnet-contrib, 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-dotnet-contrib acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.5% were successfully merged into the primary branch.
open-telemetry/opentelemetry-dotnet-contrib has a recorded first-timer success rate of 68.8%. 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 69.5 places open-telemetry/opentelemetry-dotnet-contrib in the Welcoming tier.
The external pull request merge rate is 79.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, open-telemetry/opentelemetry-dotnet-contrib 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-dotnet-contrib 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.