open-telemetry/opentelemetry-dotnet

The OpenTelemetry .NET Client

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 4 minutes ago
Added to GitGenius on April 2nd, 2023
Created on May 7th, 2019
Open Issues & Pull Requests: 139 (+1)
Number of forks: 894
Total Stargazers: 3,742 (+0)
Total Subscribers: 65 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.8 days
Mean response time: 238.3 days
90th percentile: 887.3 days
Tracked items: 581

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 55% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "pkg:OpenTelemetry" is answered fastest, typically in about 13 hours, while "metrics" waits about 4 months. Almost all tracked open issues have seen activity in the last three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 121
New in 7 days: 6
Closed in 7 days: 6
Avg open age: 750 days
Stale 30+ days: 5
Stale 90+ days: 0

Recent activity

Opened in 7 days: 6
Closed in 7 days: 6
Comments in 7 days: 12
Events in 7 days: 177

Top labels

  • enhancement (311)
  • bug (234)
  • Stale (187)
  • pkg:OpenTelemetry (125)
  • question (112)
  • pkg:OpenTelemetry.Exporter.OpenTelemetryProtocol (109)
  • help wanted (77)
  • needs-triage (66)

Detailed Description

OpenTelemetry .NET is the official .NET implementation of the OpenTelemetry standard, providing comprehensive observability capabilities for .NET and .NET Framework applications. Written in C#, the project delivers a complete SDK for instrumenting applications with distributed tracing, metrics collection, and structured logging—the three core telemetry signals defined by the OpenTelemetry specification. The project maintains stable status across all three signals, though certain pre-release components may still undergo breaking changes before reaching full stability.

The repository supports all officially supported versions of .NET and .NET Framework except .NET Framework 3.5, making it broadly compatible with modern and legacy Windows-based .NET deployments. The project is organized around a modular architecture where components are shipped as separate NuGet packages, allowing developers to adopt only the functionality they need. Core components include the OpenTelemetry API, the main SDK, and hosting extensions for dependency injection scenarios. The project provides multiple exporter libraries for sending telemetry data to various backends: Console and in-memory exporters for development and testing, the OpenTelemetry Protocol (OTLP) exporter for standards-compliant backends, Prometheus exporters for metrics collection via both AspNetCore and HttpListener transports, and a deprecated Zipkin exporter for distributed tracing.

The repository emphasizes extensibility, enabling developers to build custom instrumentation libraries, exporters for any of the three signals, processors for logs and traces, and samplers for traces. Getting started guides are provided for both ASP.NET Core and console applications across all three telemetry domains, with additional documentation covering SDK customization and best practices. The project includes troubleshooting resources and maintains detailed README and changelog files for each individual component.

Activity data reveals substantial ongoing development and maintenance. The repository shares contributors with major projects including Microsoft's VSCode and TypeScript implementations as well as the Rust language project, indicating cross-ecosystem involvement in observability standards.

The project publishes nightly builds to MyGet for early access and maintains a formal release process with published milestones and release notes. Starting with version 1.10.0, all NuGet packages include DLLs digitally signed using Sigstore, with verification possible via the cosign tool. From version 1.14.0 onward, packages include GitHub Artifact attestations for additional supply chain security. The project maintains an active community with weekly meetings alternating between 9AM and 4PM PT on Tuesdays, coordinated through the OpenTelemetry community calendar.