Type to search.

Elastic Distribution of OpenTelemetry .NET release notes

Serverless Observability

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Review the changes, fixes, and more in each version of Elastic Distribution of OpenTelemetry .NET.

To check for security updates, go to Security announcements for the Elastic stack.

  • Update to latest upstream packages (SDK 1.20.1 and instrumentation 1.18.0). #452
  • Notify subscribers when OpAMP remote configuration has no usable log level. #453
  • Fix to ensure OTEL_DOTNET_AUTO_METRICS_INSTRUMENTATION_ENABLED is honored. #451
  • Fix redaction of header secrets, such as OTLP authorization headers, in the diagnostics output for IConfiguration and for machine and user environment variables. #455
  • Fix options equality. #457
  • Fix safety timer. #461
  • Fix low-severity cleanups. #463
  • Fix file logger disposal. #464
  • Fix orphaned composite logger. #465
  • Fix pre-activation logger ownership across concurrent bootstrap flows. #467
  • Update the operator dockerfile to align with upstream #437
  • Update to latest upstream packages (SDK 1.19.1 and instrumentation 1.17.0). #437
  • Add ASP.NET classic example. #97
  • Use UserAgentProductIdentifier rather than custom HttpClientFactory #438
  • Avoid multiple activation attempts on the composite logger. #424
  • Improve diagnostic logging for loaded assemblies. #416
  • Update to 1.16.x SDK, zero-code instrumentation distribution and latest instrumentation packages. #426
Important

This release includes a behavior change by re-enabling IncludeScopes for logging. This ensures richer attributes on logs, but can increase storage costs. This is now safe to use using EDOT collector and managed OTLP endpoints.

Note

This release updates to the latest upstream releases for the OpenTelemetry SDK, contrib and auto-instrumentation components. For core components the version used is 1.15.3 and for auto-instrumentation it is 1.15.0.

  • Add Central Configuration (using OpAMP) Support. #392
  • Reenable include scopes by default. #399
  • Update to latest upstream packages. #409
Note

This release includes preparatory work for OpAMP configuration and central configuration.These options do not currently have any impact and should not be used.

  • Add initial config options to configure OpAmp client. #372
  • Redact and log the OpAmp header option. #374
  • Update k8s operator to use wolfi-base. #383
  • Update to latest upstream packages. #385
  • Fix file logging when configured in appSettings. #370
  • Ensure environment variable resource attributes apply after EDOT defaults. #368
  • Upgrade to .NET 10 SDK #339
  • Update upstream OTel package dependencies. 1.14.0 for SDK and contrib, 1.13.0 for instrumentation. #343
  • Enhance diagnostic logging capabilities. #348
  • Fix version numbers in packaging of PowerShell module. #297
  • Ensure correct execution order for user-provided delegates. #325
  • Update to 1.12.x upstream packages. #287
  • Treat EventLevel.Verbose as debug log level when subscribing to SDK events for diagnostics. #288
  • Log after adding AspNetCore trace instrumentation. Improves the trace logging for diagnostic and support purposes. #262
  • No longer default to IncludeScopes. The upstream SDK isn't spec-compliant regarding not exporting duplicate attributes. As such, when using IncludeScopes in ASP.NET Core, log entries often include a duplicated RequestId attribute. The Elasticsearch` exporter component of the collector expects the data to comply with the spec and, for performance reasons, doesn't attempt to de-duplicate, resulting in export errors for the log record. EDOT .NET no longer enables IncludeScopes by default as a partial workaround. This will be re-enabled in a future release, once the risk of data loss is resolved upstream. #265
  • Removed invalid prefix from minver command. #261
  • Update docs for GA. #256
  • Simplify reflection to work on classic ASP.NET and singlefile publish. #257
  • Ignore warning for unstable dependencies. #258
  • Disable generateapichanges for release. #259