Technologies Supported by EDOT .NET SDK

EDOT .NET is a distribution of OpenTelemetry .NET SDK, it thus inherits all the supported technologies from the upstream SDK.

.NET Frameworks

This includes the currently supported Microsoft .NET frameworks:

Framework End of support
.NET Framework 4.6.2 12th Jan 2027
.NET Framework 4.7 Not announced
.NET Framework 4.7.1 Not announced
.NET Framework 4.7.2 Not announced
.NET Framework 4.8 Not announced
.NET Framework 4.8.1 Not announced
.NET 8 10th November 2026
.NET 9 12th May 2026
.NET 10 (preview)¹ Not announced
  1. Official support begins once this is released (generally available) in November 2025

For further details, see Microsoft .NET Framework support dates and .NET Support Policy.

Instrumentations

Instrumentation for .NET can occur in three main ways:

  1. Built-in OpenTelemetry native instrumentation (the end goal for OpenTelemetry), where libraries are instrumented using the .NET APIs, requiring no bridging libraries to be observed. Many Microsoft recent libraries implement OpenTelemetry native instrumentation, and many third parties are working on such improvements. When native OTel instrumentation exists, it may be observed directly by the OpenTelemetry SDK (and, by extension, EDOT .NET) by calling AddSource to register the ActivitySource used by the instrumented code.
  2. Contrib instrumentation packages. These packages “bridge” existing telemetry from libraries to emit or enrich OpenTelemetry spans and metrics. Some packages have no dependencies and are included with EDOT .NET by default. Others, which bring in transitive dependencies, can be added to applications and registered with the OpenTelemetry SDK. EDOT .NET provides an instrumentation assembly scanning feature to register any contrib instrumentation without code changes.
  3. Additional instrumentation is available for some components and libraries when using the profiler-based zero code installation, for which EDOT .NET does not add any additional instrumentation. The current list supported upstream can be found in the .NET zero-code documentation.

See also the EDOT .NET opinionated defaults for behaviour that might differ from the OpenTelemetry NET SDK defaults.