Releases: thorstenalpers/OpenTelemetryExtension.Configuration
Releases · thorstenalpers/OpenTelemetryExtension.Configuration
OpenTelemetryExtension.Configuration 2.1.0
v2.1.0
Released: 2026-06-12
Added
net8.0target framework. The library now shipsnetstandard2.0,net8.0
andnet10.0assets. .NET 8 (LTS) consumers previously resolved the
netstandard2.0asset, which excludes ASP.NET Core instrumentation and the
ExcludedPathsrequest filter; they now get full feature parity with
net10.0. .NET 9 apps resolve thenet8.0asset.
OpenTelemetryExtension.Configuration 2.0.1
v2.0.1
Released: 2026-06-12
Changed
- Updated
OpenTelemetry.Exporter.OpenTelemetryProtocoland
OpenTelemetry.Extensions.Hostingto 1.16.0.
Fixed
- OTLP signal URLs no longer contain a double slash when the endpoint has no
path:http://localhost:4318now exports tohttp://localhost:4318/v1/traces
instead ofhttp://localhost:4318//v1/traces. - The
service.versionresource attribute now reports the host application's
version (entry assembly) instead of the library's own version. AddTelemetry(Action<TelemetryOptions>)now throws the documented
ArgumentNullExceptioninstead of aNullReferenceExceptionwhen the
configure delegate isnull.
OpenTelemetryExtension.Configuration 2.0.0
v2.0.0
Released: 2026-06-10
Added
AdditionalTracingSources— extraActivitySourcenames to collect traces from, registered viaAddSource. Enables source-based instrumentation (e.g.Npgsql,MySqlConnector, your own app sources) purely fromappsettings.json— no code required.AdditionalMeters— extraMeternames to collect metrics from, registered viaAddMeter.- Custom configuration section — the
AddTelemetry(IConfiguration)overloads accept an optionalsectionNameparameter to bind a section other than the default"Telemetry".
Changed
Enablednow defaults totrue— telemetry is on out of the box; set"Enabled": falseto turn it off.- The
netstandard2.0build no longer pulls in ASP.NET Core dependencies —OpenTelemetry.Instrumentation.AspNetCoreis only referenced by thenet10.0target, so WPF and console consumers stay lean. - The local OpenObserve backend setups (Helm chart, Docker Compose) ship with a fixed Basic Auth header so the README examples work copy-paste.
- Updated all NuGet dependencies to their latest versions.
Removed
EnableSqlClientInstrumentationand the built-inOpenTelemetry.Instrumentation.SqlClientdependency. Database instrumentation is driver-specific and is now added via theConfigureTracinghook (e.g.AddSqlClientInstrumentation(),AddEntityFrameworkCoreInstrumentation()) or, for drivers with a built-inActivitySource, viaAdditionalTracingSources— see the README's Databases section for migration examples.
OpenTelemetryExtension.Configuration 1.1.1
v1.1.1
Maintenance release — documentation, infrastructure and tooling only. No changes
to the library code or public API.
Documentation
- README restructured for clarity — full configuration reference and external
links moved to the end, backend docs trimmed to Aspire, Jaeger and OpenObserve. - Added an explanation of the
Configure*hooks, Meters and Sources, with
examples and links to the OpenTelemetry and Microsoft docs. - Added "Running Locally with a Backend" guide (start script → launch profile → UI)
and backend UI preview images.
Infrastructure
- Added .NET Aspire Dashboard setup for both Docker Compose and Helm (with
NodePort services), and registered the infrastructure files in the solution.
Tooling
- Replaced the
releasecommand with anauto-releaseskill (helper scripts and
a release-notes template). - Added an end-to-end telemetry smoke-test (Helm + OpenObserve) that verifies
exported data actually arrives via the OpenObserve query API.
OpenTelemetryExtension.Configuration 1.1.0
v1.1.0
New Features
SampleRatio— configure trace sampling viaappsettings.json(1.0= all,0.1= 10%). UsesParentBased(TraceIdRatioBased)sampler.ResourceAttributes— add arbitrary OpenTelemetry resource attributes (e.g.team,region) viaappsettings.json.ExcludedPaths— replacesExcludeHealthChecks. Accepts a list of paths to exclude from tracing (default:["/health"]).IncludeScopes— controls whether log scopes are included in exported log records (default:true).IncludeFormattedMessage— controls whether the formatted log message is included in exported log records (default:true).
Changes
EnableSqlClientInstrumentationdefault changed fromtruetofalse— opt-in, as not all applications use SQL.ExcludeHealthChecksremoved — replaced by the more flexibleExcludedPaths.
Improvements
- README rewritten for clarity — cleaner getting started, expanded backend examples.
TreatWarningsAsErrorsenabled across all projects.- CI now also runs on pull requests.
- GitHub Actions: replaced deprecated
actions/create-release@v1withsoftprops/action-gh-release@v2. RepositoryType,PackageReleaseNotesand dynamic copyright added to NuGet package metadata.
OpenTelemetryExtension.Configuration 1.0.2
What's Changed
v1.0.2
What's Changed
- Added multi-targeting support for netstandard2.0 and net8.0
- Improved compatibility across modern and legacy .NET applications
- Updated package metadata and build configuration
OpenTelemetryExtension.Configuration 1.0.1
What's Changed
v1.0.1
What's Changed
- Improved NuGet package description
- Updated package tags
OpenTelemetryExtension.Configuration 1.0.0
What's Changed
v1.0.0
What's Changed
- Added
AddTelemetry()extension supporting bothIConfigurationandAction<TelemetryOptions>registration - Added
TelemetryOptionswith full appsettings.json support and XML documentation - Tracing, metrics and logging configurable independently via
EnableTracing,EnableMetrics,EnableLogging - ASP.NET Core, HttpClient, SqlClient and runtime instrumentation with individual opt-in flags
- OTLP endpoint path handling fixed:
/v1/traces|metrics|logsonly appended forHttpProtobuf, not forGrpc ConfigureTracing,ConfigureMetrics,ConfigureLoggingcallbacks for custom instrumentation (e.g. MySQL, Redis)- Health check endpoints excludable from tracing via
ExcludeHealthChecks