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).

OpenTelemetry for .NET supports all officially supported versions of .NET and .NET Framework except for .NET Framework 3.5 SP1.

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

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.

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.

Add the ServiceDefaults project to the solution using Add New Project in Visual Studio, or use dotnet new aspire-servicedefaults --output ServiceDefaults. Reference the ServiceDefaults project from your ASP.NET application. In Visual Studio use Add > Project Reference and select the ServiceDefaults project. Call its OpenTelemetry setup function as part of your application builder initialization.

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 …

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.

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.

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

3 weeks ago - [9]: RabbitMq.Client needs bytecode instrumentation only for 5.* and 6.* versions, 7.0.0+ uses only source instrumentation.

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...

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

The API definition doesn't use anything specific to OpenTelemetry. It uses the .NET APIs for observability. Use the NuGet Package Manager or command line to add the following NuGet packages: dotnet add package OpenTelemetry.Exporter.Console dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol dotnet add package OpenTelemetry.Exporter.Prometheus.AspNetCore --prerelease dotnet add package OpenTelemetry.Exporter.Zipkin dotnet add package OpenTelemetry.Extensions.Hosting dotnet add package OpenTelemetry.Instrumentation.AspNetCore dotnet add package OpenTelemetry.Instrumentation.Http

3 weeks ago - [2] Notice that applications launched via dotnet MyApp.dll have process name dotnet or dotnet.exe. A resource is the immutable representation of the entity producing the telemetry. See Resource semantic conventions for more details. The following resource detectors are included and enabled by default: Propagators allow applications to share context. See the OpenTelemetry specification for more details.

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

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.

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 ...