This repository includes only what is defined in the OpenTelemetry Specification and is shipped as separate packages through NuGet. Each component has an individual README.md and CHANGELOG.md file which covers the instructions on how to install and get started, and details about the individual changes made (respectively).

This section introduces how to use OpenTelemetry with .NET to generate and collect telemetry data such as metrics, logs, and traces using the OpenTelemetry API and SDKs.

using OpenTelemetry; using OpenTelemetry.Exporter; using OpenTelemetry.Resources; using OpenTelemetry.Trace; using OpenTelemetry.Metrics; using OpenTelemetry.Logs; var builder = WebApplication.CreateBuilder(args); // Configure resource attributes var serviceName = "my-dotnet-service"; var serviceVersion = "1.0.0"; // Add OpenTelemetry services builder.Services.AddOpenTelemetry() .ConfigureResource(resource => resource .AddService( serviceName: serviceName, serviceVersion: serviceVersion) .AddAttributes(new Dictionary<string, object> { ["deployment.environment"] = "production", ["service.namesp

December 21, 2021 - I’m pleased to report that OTel tracing is essentially complete and more-or-less released concurrently with the launch of .NET 6; OTel metrics is not quite done yet, however, hence the core OTel packages still being release candidates at the moment. Due to demand from users and customers, Petabridge has started developing a Phobos 2.0 product which will replace our current OpenTracing + App.Metrics with OpenTelemetry tracing and metrics.

These opinionated guides make it easy to get started. They include all the binaries, configuration, and connection parameters you need to set up OpenTelemetry for Grafana Cloud. Ensure you have a .NET development environment and an application using .NET 6+ or .NET Framework version 4.6.2 or higher.

August 12, 2025 - If you are not using a minimal API with ASP.NET Core, that’s OK — you can use OpenTelemetry .NET with other frameworks as well. For a complete list of libraries for supported frameworks, see the registry. For more elaborate examples, see examples. To begin, set up an environment in a new directory called dotnet-simple.

March 11, 2025 - In this comprehensive guide, you'll learn how to implement OpenTelemetry logging in a .NET 6+ Web API application and visualize logs using OpenObserve.

December 7, 2025 - By following this guide, you should now have a working OpenTelemetry setup that captures traces and metrics from your application. As you become more comfortable with OpenTelemetry, explore advanced features like custom metrics, context propagation, and integration with various observability backends. Happy monitoring! dotnet opentelemetry observability monitoring distributed-tracing

February 6, 2026 - OpenTelemetry's metrics implementation in .NET builds on System.Diagnostics.Metrics, which was introduced in .NET 6.

I have an application running in .NET6 and I would like to integrate it with OpenTelemetry for metrics gathering. Documentation I'm following is: https://github.com/open-telemetry/opentelemetry-dot...

April 2, 2024 - It best supports modern .NET runtimes, .NET 6.0 and later. We’d love to hear about other scenarios you think we should focus on next. The types we introduce in the distribution are to support an easy switch from the “vanilla” OpenTelemetry SDK with no (or minimal) code changes.

3 weeks ago - OpenTelemetry .NET Automatic Instrumentation should work with all officially supported operating systems and versions of .NET. The minimal supported version of .NET Framework is 4.6.2. ... Instrumenting self-contained applications is supported through NuGet packages. Note that a self-contained application is automatically generated in .NET 7+ whenever the dotnet publish or dotnet build command is used with a Runtime Identifier (RID) parameter, for example when -r or --runtime is used when running the command.

January 14, 2026 - If you prefer to use OpenTelemetry APIs instead of System.Diagnostics APIs, you can refer to the OpenTelemetry API Shim docs for tracing. This page uses a modified version of the example app from Getting Started to help you learn about manual instrumentation. You don’t have to use the example app: if you want to instrument your own app or library, follow the instructions here to adapt the process to your own code. .NET SDK 6+ To begin, set up an environment in a new directory called dotnet-otel-example.

June 21, 2023 - To configure and run a local collector we will need a few things. First, do you have docker desktop? If not, please go get it for your OS. Second, we will need to create a yaml file for the collector to be built by, and lastly we will need to add another package to our project, OpenTelemetry.Exporter.OpenTelemetryProtocol.

April 23, 2026 - [9]: RabbitMq.Client needs bytecode instrumentation only for 5.* and 6.* versions, 7.0.0+ uses only source instrumentation.

March 19, 2021 - If you are not a library author, you can skip this section. Popular libraries in the .NET ecosystem (ASP.NET Core, grpc-dotnet, SQLClient) are already instrumented and ready for to you consume observability telemetry. The System.Diagnostics APIs in .NET contain an implementation of the OpenTelemetry API specification.

November 26, 2023 - Looking to use distributed tracing in your .NET application? Follow this tutorial for using OpenTelemetry C# automatic and manual instrumentation

February 28, 2024 - 6. Leverage opentelemetry-dotnet-contrib: The opentelemetry-dotnet-contrib repository contains additional instrumentation packages and exporters for .NET.

This repository contains set of components extending functionality of the OpenTelemetry .NET SDK. Instrumentation libraries, exporters, and other components can find their home here. - open-telemet...

January 27, 2025 - Getting Started with OpenTelemetry in .NET OpenTelemetry is an open-source framework for observability that provides tools, APIs, and SDKs to help developers generate, collect, and export telemetry …