Bump the nuget group with 1 update #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated OpenTelemetry.Instrumentation.AspNetCore from 1.0.0-rc9.4 to 1.8.1.
Release notes
Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.
1.8.1
OpenTelemetry.Instrumentation.AspNetCore
values detected in the query string component of requests are replaced with
the text
Redactedwhen building theurl.querytag. For example,?key1=value1&key2=value2becomes?key1=Redacted&key2=Redacted. You candisable this redaction by setting the environment variable
OTEL_DOTNET_EXPERIMENTAL_ASPNETCORE_DISABLE_URL_QUERY_REDACTIONtotrue.(#5532)
1.8.0
If you're interested in knowing all of the changes that went into 1.8.0 release, please go through the release notes of all the previous pre-release versions for 1.8.0:
Changes in 1.8.0:
OpenTelemetry.Exporter.Console
ActivitySource.Versionproperty.(#5472)
OpenTelemetry.Exporter.OpenTelemetryProtocol
OtlpExporterwill no longer throw an exception (even on .NET Core 3.1)when the
System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupportAppContextswitch is NOT set AND usingOtlpExportProtocol.Grpcto send to an insecure ("http") endpoint.
System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupportis not required to be set when using .NET 5 or newer.
(#5486)
Replaced environment variable
OTEL_DOTNET_EXPERIMENTAL_OTLP_ENABLE_INMEMORY_RETRYwithOTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY.OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRYwhen set to
in_memorywill enable automatic retries in case of transientfailures during data export to an OTLP endpoint.
(#5495)
1.8.0-rc.1
OpenTelemetry
TracerProviders can now have a sampler configured via theOTEL_TRACES_SAMPLERenvironment variable. The supported values are:always_off,always_on,traceidratio,parentbased_always_on,parentbased_always_off, andparentbased_traceidratio. The optionstraceidratioandparentbased_traceidratiomay have the sampler probabilityconfigured via the
OTEL_TRACES_SAMPLER_ARGenvironment variable.For details see: OpenTelemetry Environment Variable
Specification.
(#5448)
OpenTelemetry.Exporter.Prometheus.AspNetCore
Fix serializing scope_info when buffer overflows
(#5407)
Add
target_infoto Prometheus exporters when using OpenMetrics(#5407)
OpenTelemetry.Exporter.Prometheus.HttpListener
Fix serializing scope_info when buffer overflows
(#5407)
Add
target_infoto Prometheus exporters when using OpenMetrics(#5407)
OpenTelemetry.Exporter.Zipkin
otel.library.nameandotel.library.versiontootel.scope.nameandotel.scope.versionrespectively.Old versions of attributes are deprecated, but still exported
for backward compatibility.
(#5473)
1.8.0-beta.1
OpenTelemetry
Throw NotSupportedException when using
SetErrorStatusOnExceptionmethod for Tracing in Mono Runtime and Native AOT environment because the dependentMarshal.GetExceptionPointers()API is not supported on these platforms. (#5374)Fixed an issue where
LogRecord.Attributes(orLogRecord.StateValuesalias) could become out of sync withLogRecord.Stateif either is set directly via the public setters. This was done to further mitigate issues introduced in 1.5.0 causing attributes added using custom processor(s) to be missing after upgrading. For details see:(#5169)Fixed an issue where
SimpleExemplarReservoirwas not resetting internal state for cumulative temporality. (#5230)Fixed an issue causing
LogRecords to be incorrectly reused when wrapping an instance ofBatchLogRecordExportProcessorinside anotherBaseProcessor<LogRecord>which leads to missing or incorrect data during export. (#5255)Experimental (pre-release builds only): Added support for setting
CardinalityLimit(the maximum number of data points allowed for a metric) when configuring a view (applies to individual metrics) and obsoletedMeterProviderBuilderExtensions.SetMaxMetricPointsPerMetricStream(previously applied to all metrics). The default cardinality limit for metrics remains at2000. (#5312, #5328)Updated
LogRecordto keepCategoryNameandLoggerin sync when using the experimental Log Bridge API. #5317Added
OpenTelemetryBuilderSdkExtensionsclass which contains extension methods (ConfigureResource,WithMetrics,WithTracing, and experimentalWithLogging) for theIOpenTelemetryBuilderinterface. (#5265)Added
Microsoft.Extensions.Diagnostics.Abstractionsdependency so that theIOpenTelemetryBuilder.WithMetricsextension method can configure IMetricsListener. (#5265)Experimental (pre-release builds only): The
Exemplar.FilteredTagsproperty now returns aReadOnlyFilteredTagCollectioninstance and theExemplar.LongValueproperty has been added. TheMetricPoint.GetExemplarsmethod has been replaced byMetricPoint.TryGetExemplarswhich outputs aReadOnlyExemplarCollectioninstance. These are breaking changes for metrics exporters which support exemplars. (#5386)Experimental (pre-release builds only): Added support for exemplars when using Base2 Exponential Bucket Histogram Aggregation configured via the View API. (#5396)
Experimental (pre-release builds only): Removed the
ExemplarFilter,AlwaysOffExemplarFilter,AlwaysOnExemplarFilter, andTraceBasedExemplarFilterAPIs. TheMeterProviderBuilder.SetExemplarFilterextension method now accepts anExemplarFilterTypeenumeration (which contains definitions for the supported filter typesAlwaysOff,AlwaysOn, andTraceBased) instead of anExemplarFilterinstance. This was done in response to changes made to the OpenTelemetry Metrics SDK Specification. (#5404)Experimental (pre-release builds only): The
ExemplarFilterused by SDKMeterProviders can now be controlled via theOTEL_METRICS_EXEMPLAR_FILTERenvironment variable. The supported values are:always_off,always_on, andtrace_based. For details see: OpenTelemetry Environment Variable Specification. (#5412)OpenTelemetry.Api.ProviderBuilderExtensions
IOpenTelemetryBuilderinterface to support authoring extensions which can configure multiple OpenTelemetry signals (tracing, metrics, and/or logs). (#5265)OpenTelemetry.Exporter.OpenTelemetryProtocol
Experimental (pre-release builds only): Added
LoggerProviderBuilder.AddOtlpExporterregistration extensions. #5103Removed the
OTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EXCEPTION_LOG_ATTRIBUTESenvironment variable, following the stabilization of the exception attributesexception.type,exception.message, andexception.stacktracein the OpenTelemetry Semantic Conventions. These attributes, corresponding toLogRecord.Exception, are now stable and will be automatically included in exports. (#5258)Updated
OtlpLogExporterto setbodyon the data model fromLogRecord.Bodyif{OriginalFormat}attribute is NOT found andFormattedMessageisnull. This is typically the case when using theexperimental Logs Bridge API. (#5268)
Updated
OtlpLogExporterto set instrumentation scope name on the data model fromLogRecord.Logger.NameifLogRecord.CategoryNameisnull. This is typically the case when using the experimental Logs Bridge API. (#5300)URL encoded values in
OTEL_EXPORTER_OTLP_HEADERSare now correctly decoded as it is mandated by the specification. (#5316)Experimental (pre-release builds only): Add support in
OtlpMetricExporterfor emitting exemplars supplied on Counters, Gauges, andExponentialHistograms. (#5397)
Setting
EndpointorHttpClientFactoryproperties onOtlpExporterOptionstonullwill now result in anArgumentNullExceptionbeing thrown. (#5434)Introduced experimental support for automatically retrying export to the otlp endpoint when transient network errors occur. Users can enable this feature by setting
OTEL_DOTNET_EXPERIMENTAL_OTLP_ENABLE_INMEMORY_RETRYenvironment variable to true. (#5435)... (truncated)
1.7.1
1.7.1 (stable instrumentation)
OpenTelemetry.Instrumentation.AspNetCore
Activity.Currentwas different than instance obtained fromIHttpActivityFeature.Activity. (#5136)http.routeattribute was not set on either theActivityorhttp.server.request.durationmetric generated from a request when an exception handling middleware is invoked. One caveat is that this fix does not address the problem for thehttp.server.request.durationmetric when running ASP.NET Core 8. ASP.NET Core 8 contains an equivalent fix which should ship in version 8.0.2 (see: dotnet/aspnetcore#52652). (#5135)net6.0target of this library is loaded into a .NET 7+ process and the instrumentation does not behave as expected. This is an unusual scenario that does not affect users consuming this package normally. This fix is primarily to support the opentelemetry-dotnet-instrumentation project. (#5252)OpenTelemetry.Instrumentation.Http
http.client.request.durationmetric. (#5234)1.7.0-beta.1 (pre-release instrumentation)
OpenTelemetry.Instrumentation.SqlClient
OTEL_SEMCONV_STABILITY_OPT_INenvironment variable which toggled the use of the new conventions for the server, client, and shared network attributes. Now that this suite of attributes are stable, this instrumentation will only emit the new attributes. (#5270)SqlClientInstrumentationOptionstoSqlClientTraceInstrumentationOptions. (#5285)db.statement_typeattribute. This attribute was never a part of the semantic conventions. (#5301)OpenTelemetry.Instrumentation.GrpcNetClient
OpenTelemetry.Instrumentation.Httppackage version1.6.0or greater. This is not a result of a change in theOpenTelemetry.Instrumentation.GrpcNetClientpackage therefore this also affects versions prior to this release. See this issue for details and workaround.OTEL_SEMCONV_STABILITY_OPT_INenvironment variable which toggled the use of the new conventions for the server, client, and shared network attributes. Now that this suite of attributes are stable, this instrumentation will only emit the new attributes. (#5259)GrpcClientInstrumentationOptionstoGrpcClientTraceInstrumentationOptions. (#5272)1.7.0
1.7.0 release for core components
If you're interested in knowing all of the changes that went into
1.7.0release, please go through the Release notes of all the previous pre-release versions for1.7.0.1.7.0-beta.1 release for non-core components
Note: Instrumentation libraries were not included for
1.7.0-beta.1.OpenTelemetry.Shims.OpenTracing
TracerShim(Tracer, TextMapPropagator)constructor. UseTracerShim(TracerProvider)orTracerShim(TracerProvider, TextMapPropagator)constructors. (#4862)1.7.0-rc.1
OpenTelemetry
The
AddServiceResourceBuilderextension method will now generate the sameservice.instance.idfor the lifetime of a process whenautoGenerateServiceInstanceIdistrue. (#4988)Fixed a Metrics SDK bug which led to
ExemplarReservoir.Offeralways being called regardless of whether or not theExemplarFiltersampled the measurement. (#5004) (#5016)Update Metrics SDK to override the default histogram buckets for the followingmetrics from ASP.NET Core and HttpClient runtime:
signalr.server.connection.durationkestrel.connection.durationhttp.client.connection.durationThese histogram metrics which have their
Unitass(second) will have their default histogram buckets as[ 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10, 30, 60, 120, 300 ]. (#5008) (#5021)Remove the bucket with value
0for histogram buckets for all metrics from ASP.NET Core and HttpClient. (#5021)Updated
Microsoft.Extensions.Logging.Configurationpackage version to8.0.0. (#5051)Updated
Microsoft.Extensions.Loggingpackage version to8.0.0. (#5051)Revert the default behavior of Metrics SDK for Delta aggregation. It would not reclaim unused Metric Points by default. You can enable the SDK to reclaim unused Metric Points by setting the environment variable
OTEL_DOTNET_EXPERIMENTAL_METRICS_RECLAIM_UNUSED_METRIC_POINTStotruebefore setting up theMeterProvider. (#5052)Update Metrics SDK to override the default histogram buckets for ASP.NET (.NET Framework).
Histogram metrics for the meter name
OpenTelemetry.Instrumentation.AspNetand instrument namehttp.request.server.durationwhich have theirUnitass(second) will have their default histogram buckets as[ 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10 ]. (#5063)Added
AddProcessoroverload onOpenTelemetryLoggerOptionswhich exposes the factory pattern(Func<IServiceProvider, BaseProcessor<LogRecord>> implementationFactory). (#4916)Add support for Instrumentation Scope Attributes (i.e Meter Tags), fixing issue #4563. (#5089)
Added the
ILoggingBuilder.UseOpenTelemetryexperimental API extension for registering OpenTelemetryILoggerintegration usingLoggerProviderBuilderwhich supports the full DI (IServiceCollection\IServiceProvider) API surface (mirrors tracing & metrics). (#5072)Changed the
ILoggingBuilderregistration extensions (AddOpenTelemetry&UseOpenTelemetry) to fire the optionalOpenTelemetryLoggerOptionsconfiguration delegate AFTER the "Logging:OpenTelemetry"IConfigurationsection has been applied. (#5072)OpenTelemetry.Api
System.Diagnostics.DiagnosticSourcepackage version to8.0.0. (#5051)OpenTelemetry.Api.ProviderBuilderExtensions
Microsoft.Extensions.DependencyInjection.Abstractionspackage version to8.0.0. (#5051)OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.OpenTelemetryProtocol
Made
OpenTelemetry.Exporter.OtlpLogExporterpublic. (#4979)Updated the
OpenTelemetryLoggerOptions.AddOtlpExporterextension to retrieveOtlpExporterOptionsandLogRecordExportProcessorOptionsusing theIServiceProvider/ Options API so that they can be controlled viaIConfiguration(similar to metrics and traces). (#4916)... (truncated)
1.7.0-alpha.1
OpenTelemetry
Update
AggregatorStoreto reclaim unused MetricPoints for Delta aggregation temporality. (#4486)Fixed a bug where
TracerProviderBuilderBasewas not invoking theinstrumentationFactorydelegate passed to theprotectedAddInstrumentationmethod. (#4873)Allowed metric instrument names to contain
/characters. (#4882)Breaking Change
[Tracer|Meter|Logger]ProviderBuilder.Buildextension will now throw aNotSupportedExceptionif invoked on a non-SDK builder type. Previously it would returnnull. (#4885)Updated
Microsoft.Extensions.Loggingpackage version to8.0.0-rc.1.23419.4. (#4920, #4933)OpenTelemetry.Api
Fixed a bug which caused
Tracer.StartRootSpanto generate a child span if a trace was running (Activity.Current != null). (#4890)Added a
Tracercache inside ofTracerProviderto prevent repeated calls toGetTracerfrom leaking memory. (#4906)Fix
TraceContextPropagatorby validating the first digit of the hex-encodedtrace-flagsfield of thetraceparentheader. (#4893)OpenTelemetry.Exporter.OpenTelemetryProtocol
Bumped the version of
Google.Protobufused by the project to3.22.5so that consuming applications can be published as NativeAOT successfully. Also, a new performance feature can be used instead of reflection emit, which is not AOT-compatible. Removed the dependency onSystem.Reflection.Emit.Lightweight. (#4859)Added support for
OTEL_LOGRECORD_ATTRIBUTE_VALUE_LENGTH_LIMITandOTEL_LOGRECORD_ATTRIBUTE_COUNT_LIMIT. (#4887)Added ability to export attributes corresponding to
LogRecord.Exceptioni.e.exception.type,exception.messageandexception.stacktrace. These attributes will be exported whenOTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EXCEPTION_LOG_ATTRIBUTESenvironment variable will be set totrue.NOTE: These attributes were removed in 1.6.0-rc.1 release in order to support stable release of OTLP Log Exporter. The attributes will now be available via environment variable mentioned above. (#4892)
Added ability to export attributes corresponding to
LogRecord.EventId.Idaslogrecord.event.idandLogRecord.EventId.Nameaslogrecord.event.name. The attributes will be exported whenOTEL_DOTNET_EXPERIMENTAL_OTLP_EMIT_EVENT_LOG_ATTRIBUTESwill be set totrue.NOTE: These attributes were removed in 1.6.0-rc.1 release in order to support stable release of OTLP Log Exporter. The attributes will now be available via environment variable mentioned above. (#4925)
LogRecord.CategoryNamewill now be exported as InstrumentationScopenamefield under ScopeLogs. (#4941)OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.Extensions.Hosting
OpenTelemetryBuilder.AddOpenTelemetryextension to INSERT OpenTelemetry services at the beginning of theIServiceCollectionin an attempt to provide a better experience for end users capturing telemetry in hosted services. Note that this does not guarantee that OpenTelemetry services will be initialized while other hosted services start, so it is possible to miss telemetry until OpenTelemetry services are fully initialized. (#4883)1.6.0
1.6.0 release for core components
Note: The below only shows the changes that were added to the core components post
1.6.0-rc.1release. If you're interested in knowing all of the changes that went into1.6.0release, please go through the Release notes of all the previous pre-release versions for1.6.0.OpenTelemetry
Increased the character limit of the Meter instrument name from 63 to 255.
(#4774)
Update default size for
SimpleExemplarReservoirto1.(#4803)
1.6.0-beta.1 release for non-core components
Note: Instrumentation libraries were not included for
1.6.0-beta.1.OpenTelemetry.Shims.OpenTracing
ArgumentExceptionifActivitybehind the shim spanhas an invalid context.
(#2787)
TracerShim(Tracer, TextMapPropagator)constructor.Provide
TracerShim(TracerProvider)and
TracerShim(TracerProvider, TextMapPropagator)constructors.(#4812)
1.6.0-rc.1
OpenTelemetry
measurements that were dropped due to reaching the max MetricPoints
limit.
When this feature is enabled, SDK would aggregate such measurements using a
reserved MetricPoint with a single tag with key as
otel.metric.overflowandvalue as
true. The feature is turned-off by default. You can enable it bysetting the environment variable
OTEL_DOTNET_EXPERIMENTAL_METRICS_EMIT_OVERFLOW_ATTRIBUTEtotruebeforesetting up the
MeterProvider.(#4737)
OpenTelemetry.Exporter.OpenTelemetryProtocol
Excluded attributes corresponding to
LogRecord.EventId,LogRecord.CategoryNameandLogRecord.Exceptionfrom the exported data. Thisis done as the semantic conventions for these attributes are not yet stable.
(#4781)
Added extension method for configuring export processor options for otlp log
exporter.
(#4733)
Added support for configuring the metric exporter's temporality using the
environment variable
OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCEasdefined in the
specification.
(#4667)
OpenTelemetry.Exporter.Prometheus.AspNetCore
(#4753)
OpenTelemetry.Exporter.Prometheus.HttpListener
(#4753)
OpenTelemetry.Extensions.Hosting
API
implementation (
OpenTelemetryBuilder.WithLogging).(#4735)
1.6.0-beta.3
OpenTelemetry.Instrumentation.AspNetCore
Removed the Activity Status Description that was being set during exceptions. Activity Status will continue to be reported as
Error. This is a breaking change.EnrichWithExceptioncan be leveragedto restore this behavior. (#5025)
Updated
http.request.methodto match specification guidelines.http.request.method.originalandhttp.request.methodwill be set to_OTHER.http.request.methodonhttp.server.request.durationmetric will be set to_OTHERhttp.request.methodis set onhttp.server.request.durationmetric or activity whenOTEL_SEMCONV_STABILITY_OPT_INenvironment variable is set tohttporhttp/dup.(#5001)
An additional attribute
error.typewill be added to activity andhttp.server.request.durationmetric when the request results in unhandled exception. The attribute value will be set to full name of exception type.The attribute will only be added when
OTEL_SEMCONV_STABILITY_OPT_INenvironment variable is set tohttporhttp/dup. (#4986)Fixed
network.protocol.versionattribute values to match the specification. (#5007)Calls to
/metricswill now be included in thehttp.server.request.durationmetric. This change may affect Prometheus pull scenario if the Prometheus server sends request to the scraping endpoint that contains/metricsin path. (#5044)Fixes the
http.routeattribute for scenarios in which it was previously missing or incorrect. Additionally, thehttp.routeattribute is now the same for both the metric andActivityemitted for a requestLastly, the
Activity.DisplayNamehas been adjusted to have the format{http.request.method} {http.route}to conform with the specification. There remain scenarios when using conventional routing or Razor pages wherehttp.routeis still incorrect. See #5056 and #5057 for more details. (#5026)Removed
network.protocol.namefromhttp.server.request.durationmetric as per spec. (#5049)OpenTelemetry.Instrumentation.Http
Removed the Activity Status Description that was being set during exceptions. Activity Status will continue to be reported as
Error. This is a breaking change.EnrichWithExceptioncan be leveraged to restore this behavior. (#5025)Updated
http.request.methodto match specification guidelines.http.request.method.originalandhttp.request.methodwill be set to_OTHER.http.request.methodonhttp.client.request.durationmetric will be set to_OTHERhttp.request.methodis set onhttp.client.request.durationmetric or activity whenOTEL_SEMCONV_STABILITY_OPT_INenvironment variable is set tohttporhttp/dup. (#5003)An additional attribute
error.typewill be added to activity andhttp.client.request.durationmetric in case of failed requests as per the specification.Users moving to
net8.0or newer frameworks from lower versions will see difference in values in case of an exception.net8.0or newer frameworks add the ability to further drill down the exceptions to a specific type through HttpRequestError enum. For lower versions, the individual types will be rolled in to a single type. This could be a breaking change if alerts are set based on the values.The attribute will only be added when
OTEL_SEMCONV_STABILITY_OPT_INenvironment variable is set tohttporhttp/dup. (#5005) (#5034)Fixed
network.protocol.versionattribute values to match the specification. (#5006)Set
network.protocol.versionvalue using the protocol version on the received response. If the request fails without response, thennetwork.protocol.versionattribute will not be set on Activity andhttp.client.request.durationmetric. (#5043)OpenTelemetry.Instrumentation.SqlClient
Microsoft.Extensions.ConfigurationandMicrosoft.Extensions.Optionspackage version to8.0.0. (#5051)1.6.0-beta.2
OpenTelemetry.Instrumentation.AspNetCore
http.server.request.durationmeasured in seconds. The OTel SDK (starting with version 1.6.0) applies custom histogram buckets for this metric to comply with the Semantic Convention for Http Metrics.This new metric is only available for users who opt-in to the new semantic convention by configuring the
OTEL_SEMCONV_STABILITY_OPT_INenvironment variable to eitherhttp(to emit only the new metric) orhttp/dup(to emit both the new and old metrics). (#4802)http.server.request.durations(seconds)0, 0.005, 0.01, 0.025, 0.05, 0.075, 0.1, 0.25, 0.5, 0.75, 1, 2.5, 5, 7.5, 10http.server.durationms(milliseconds)0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000Note: the older
http.server.durationmetric andOTEL_SEMCONV_STABILITY_OPT_INenvironment variable will eventually be removed after the HTTP semantic conventions are marked stable. At which time this instrumentation can publish a stable release. Refer to the specification for more information regarding the new HTTP semantic conventions for both spans and metrics.Following metrics will now be enabled by default when targeting
.NET8.0or newer framework:Meter :
Microsoft.AspNetCore.Hostinghttp.server.request.durationhttp.server.active_requestsMeter :
Microsoft.AspNetCore.Server.Kestrelkestrel.active_connectionskestrel.connection.durationkestrel.rejected_connectionskestrel.queued_connectionskestrel.queued_requestskestrel.upgraded_connectionskestrel.tls_handshake.durationkestrel.active_tls_handshakesMeter :
Microsoft.AspNetCore.Http.Connectionssignalr.server.connection.durationsignalr.server.active_connectionsMeter :
Microsoft.AspNetCore.Routingaspnetcore.routing.match_attemptsMeter :
Microsoft.AspNetCore.Diagnosticsaspnetcore.diagnostics.exceptionsMeter :
Microsoft.AspNetCore.RateLimitingaspnetcore.rate_limiting.active_request_leasesaspnetcore.rate_limiting.request_lease.durationaspnetcore.rate_limiting.queued_requestsaspnetcore.rate_limiting.request.time_in_queueaspnetcore.rate_limiting.requestsFor details about each individual metric check ASP.NET Core docs page.
... (truncated)
1.6.0-alpha.1
OpenTelemetry
Add back support for Exemplars. See
exemplars for
instructions to enable exemplars.
(#4553)
Added Logs Bridge
API
implementation (
Sdk.CreateLoggerProviderBuilder, etc.).(#4433)
Obsoleted
LogRecord.LogLevelin favor of theLogRecord.Severitypropertywhich matches the OpenTelemetry Specification > Logs DataModel > Severity
definition.
(#4433)
Added
LogRecord.Loggerproperty to access the OpenTelemetry Specification >Instrumentation
Scope
provided during Logger creation.
(#4433)
Fix the issue of potentially running into the
ArgumentException:An instance of EventSource with Guid af2d5796-946b-50cb-5f76-166a609afcbb already exists.when using any of the following exporters:ConsoleExporter,OtlpExporter,ZipkinExporter,JaegerExporter.OpenTelemetry.Api
Updated
System.Diagnostics.DiagnosticSourcepackage version to7.0.2.(#4576)
Breaking change In order to make
RuntimeContextcompatible withahead-of-time compilation (AOT),
RuntimeContext.ContextSlotTypecan only beassigned one of the following types:
AsyncLocalRuntimeContextSlot<>,ThreadLocalRuntimeContextSlot<>, andRemotingRuntimeContextSlot<>. ASystem.NotSupportedExceptionwill be thrown if you try to assign any typeother than the three types mentioned.
(#4542)
Added Logs Bridge
API
implementation (
LoggerProviderBuilder,LoggerProvider,Logger, etc.).(#4433)
OpenTelemetry.Api.ProviderBuilderExtensions
API
... (truncated)
1.5.1
OpenTelemetry
Fixed a breaking change causing
LogRecord.Stateto benullwhere it was previously set to a valid value whenOpenTelemetryLoggerOptions.ParseStateValuesisfalseand states implementIReadOnlyListorIEnumerableofKeyValuePair<string, object>s. (#4609)Breaking Change Removed the support for parsing
TStatetypes passed to theILogger.Log<TState>API whenParseStateValuesis true andTStatedoes not implement eitherIReadOnlyList<KeyValuePair<string, object>>orIEnumerable<KeyValuePair<string, object>>. This feature was first introduced in the1.5.0stable release with #4334 and has been removed because it makes the OpenTelemetry .NET SDK incompatible with native AOT. (#4614)1.5.1-beta.1
For all the four instrumentation libraries: AspNetCore, HttpClient, GrpcNetClient, SqlClient:
the
OTEL_SEMCONV_STABILITY_OPT_INenvironment variable. This allows for atransition period for users to experiment with the new semantic conventions
and adapt as necessary. The environment variable supports the following
values:
http- emit the new, frozen (proposed for stable) HTTP and networkingattributes, and stop emitting the old experimental HTTP and networking
attributes that the instrumentation emitted previously.
http/dup- emit both the old and the frozen (proposed for stable) HTTPand networking attributes, allowing for a more seamless transition.
emitting the same HTTP and network semantic conventions that were emitted in
1.5.0-beta.1.network semantic conventions are marked stable. At which time this
instrumentation can receive a stable release, and the old HTTP and
network semantic conventions will no longer be supported. Refer to the
specification for more information regarding the new HTTP and network
semantic conventions for both spans and metrics.
OpenTelemetry.Instrumentation.AspNetCore
and tags are added to an Activity during sampling then that Activity would be dropped.
(#4637)
1.5.0
OpenTelemetry
Fixed a bug introduced by
#4508 in
1.5.0-rc.1 which caused the "Build" extension to return
nullwhen performingchained/fluent calls.
(#4529)
Marked
Exemplarsand related APIsinternalas the spec forExemplarsisnot stable yet. This would be added back in the
1.6.*prerelease versionsright after
1.5.0stable version is released.(#4533)
OpenTelemetry.Api.ProviderBuilderExtensions
IServiceCollection.ConfigureOpenTelemetryMeterProvideroverloadwhich may be used to configure
MeterProviderBuilders while theIServiceCollectionis modifiable (before theIServiceProviderhas beencreated).
(#4517)
OpenTelemetry.Exporter.Console
Exemplars. This would be added back in the1.6.*prerelease versions right after1.5.0stable version is released.(#4533)
OpenTelemetry.Exporter.OpenTelemetryProtocol
Exemplars. This would be added back in the1.6.*prerelease versions right after1.5.0stable version is released.(#4533)
OpenTelemetry.Instrumentation.AspNetCore
Fix issue where baggage gets cleared when the ASP.NET Core Activity
is stopped. The instrumentation no longer clears baggage. One problem
this caused was that it prevented Activity processors from accessing baggage
during their
OnEndcall.(#4274)
Added direct reference to
System.Text.Encodings.Webwith minimum version of4.7.2due to CVE-2021-26701.This impacts target frameworks
netstandard2.0andnetstandard2.1which has areference to
Microsoft.AspNetCore.Http.Abstractionsthat depends onSystem.Text.Encodings.Web>= 4.5.0.(#4399)
Improve perf by avoiding boxing of common status codes values.
(#4360,
... (truncated)
1.5.0-rc.1
OpenTelemetry
The default resource provided by
ResourceBuilder.CreateDefault()now addsthe
telemetry.sdk.*attributes defined in thespecification.
(#4369)
Fixed an issue with
HashCodecomputations throwing exceptions on .NETStandard 2.1 targets.
(#4362)
Update value of the resource attribute
telemetry.sdk.versionto show the tagname which resembles the package version of the SDK.
(#4375)
Obsoleted
StateandStateValuesproperties and addedBodyandAttributesproperties onLogRecord. Note:LogRecord.AttributesandLogRecord.StateValuespoint to the same data. "Attributes" is what theOpenTelemetry Specification defines so this was changed for clarity &
consistency with the specification.
(#4334)
Tweaked the behavior of the
OpenTelemetryLoggerOptions.ParseStateValuesflag:
LogRecord.Attributes(akaLogRecord.StateValues) are now automaticallyincluded for all log messages with states implementing
IReadOnlyListorIEnumerable.OpenTelemetryLoggerOptions.ParseStateValuesis now used to tell the SDK toparse (using reflection) attributes for custom states which do not implement
IReadOnlyListorIEnumerable. Only top-level properties are included.LogRecord.Statewill only be set to the raw state object if no attributesare found.
See #4334
for details.
If a template (
{OriginalFormat}attribute) cannot be found on log messages aformatted message will now automatically be generated (even if
OpenTelemetryLoggerOptions.IncludeFormattedMessageis set tofalse).(#4334)
OpenTelemetry.Api.ProviderBuilderExtensions
TracerProviderBuilder.AddInstrumentation(IServiceProvider, TracerProvider)factory extension from being called during construction of the SDK
TracerProvider.... (truncated)
1.5.0-alpha.2
OpenTelemetry
Enabling
SetErrorStatusOnExceptionon TracerProvider will now set theStatusproperty on Activity toActivityStatusCode.Errorin case of an error. This will be done in addition to current behavior of settingotel.status_codetag on activity. (#4336)Add support for configuring the Base2 Exponential Bucket Histogram Aggregation using the
AddViewAPI. This aggregation is supported by OTLP but not yet by Prometheus. (#4337)Implementation of
SuppressInstrumentationScopechanged to improve performance. (#4304)OpenTelemetry.Api
OpenTelemetry.Api.ProviderBuilderExtensions
OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.InMemory
MetricSnapshotof a histogram did not capture the min and max values. (#4306)OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
Add support for exporting histograms aggregated using the Base2 Exponential Bucket Histogram Aggregation. (#4337)
Added support to set
TraceStatewhen converting the System.Diagnostics.Activity object to its corresponding OpenTelemetry.Proto.Trace.V1.Span object. (#4331)OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
OpenTelemetry.Exporter.Zipkin
OpenTelemetry.Extensions.Hosting
OpenTelemetry.Extensions.Propagators
1.5.0-alpha.1
OpenTelemetry
Added Exemplar support. See exemplars for instructions to enable exemplars.
Added
AddDetectorfactory overload onResourceBuilder. (#4261)OpenTelemetry.Api
OpenTelemetry.Api.ProviderBuilderExtensions
OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
Google.Protobufused by the project to3.22.0sothat a new performance feature can be used instead of reflection. Removed the
dependency on
System.Reflection.Emit.Lightweight.(#4201)
OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.Exporter.Zipkin
OpenTelemetry.Extensions.Hosting
OpenTelemetry.Extensions.Propagators
1.4.0
1.4.0
This is the stable release encompassing work from 1.4.0-alpha.1 to 1.4.0-rc.4
OpenTelemetry
OpenTelemetry.Api
OpenTelemetry.Api.ProviderBuilderExtensions
OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
AddOtlpExporterextension methods will now always create a new options instance when named options are NOT used. (#4200)OpenTelemetry.Exporter.Zipkin
OpenTelemetry.Extensions.Hosting
AddOpenTelemetryTracing,AddOpenTelemetryMetrics,Configure, &GetServices. (#4071)OpenTelemetry.Extensions.Propagators
1.0.0-rc9.14
OpenTelemetry.Exporter.ZPages
OpenTelemetry.Instrumentation.AspNetCore
OpenTelemetry.Instrumentation.GrpcNetClient
OpenTelemetry.Instrumentation.Http
OpenTelemetry.Instrumentation.SqlClient
OpenTelemetry.Shims.OpenTracing
1.4.0-rc.4
OpenTelemetry
Removed the dependency on System.Reflection.Emit.Lightweight (#4140)
Moved the
AddOpenTelemetryextension into theOpenTelemetry.Extensions.Hostingpackage so that theStartWithHostAPIcould be removed. (#4174)
OpenTelemetry.Api
OpenTelemetry.Api.ProviderBuilderExtensions
OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.Exporter.Zipkin
OpenTelemetry.Exporter.ZPages
OpenTelemetry.Extensions.Hosting
AddOpenTelemetryextension from SDK and removedStartWithHost.AddOpenTelemetrynow registers theIHostedServiceused to start collecting traces and/or metrics. (#4174)OpenTelemetry.Extensions.Propagators
OpenTelemetry.Instrumentation.AspNetCore
OpenTelemetry.Instrumentation.GrpcNetClient
OpenTelemetry.Instrumentation.Http
OpenTelemetry.Instrumentation.SqlClient
OpenTelemetry.Shims.OpenTracing
1.4.0-rc.3
OpenTelemetry
Removed the dependency on Microsoft.Extensions.Configuration.EnvironmentVariables (#4092)
Removed the explicit reference to Microsoft.Extensions.Options version 5.0 and reverted back to the transitive reference of version 3.1 (#4093)
Added
SetSampler,AddProcessor, &AddReaderfactory extensions. (#4103)OpenTelemetry.Api
OpenTelemetry.Api.ProviderBuilderExtensions
Removed
ConfigureBuilderfrom the public API. (#4103)Renamed package from
OpenTelemetry.Extensions.DependencyInjectiontoOpenTelemetry.Api.ProviderBuilderExtensions. (#4125)OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.Exporter.Zipkin
FormatExceptionand instead log a warning. (#4095)OpenTelemetry.Exporter.ZPages
OpenTelemetry.Extensions.Hosting
OpenTelemetry.Extensions.Propagators
OpenTelemetry.Instrumentation.AspNetCore
OpenTelemetry.Instrumentation.GrpcNetClient
OpenTelemetry.Instrumentation.Http
OpenTelemetry.Instrumentation.SqlClient
... (truncated)
1.4.0-rc.2
1.4.0-rc.2
OpenTelemetry
string[]andobject[]to aKeyValuePair<string, object>[]. This results in faster copying of the metric dimensions required forMetricPointlookup on the hot path (#4059)OpenTelemetry.Api
OpenTelemetry.Exporter.Console
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
AddOtlpExporterextension methods, configuration delegates will be executed inline and not through Options API when named options are NOT used. (#4058)OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.Exporter.Zipkin
OpenTelemetry.Extensions.DependencyInjection
OpenTelemetry.Extensions.Hosting
1.0.0-rc9.11
OpenTelemetry.Extensions.Propagators
OpenTelemetry.Exporter.ZPages
OpenTelemetry.Instrumentation.AspNetCore
OpenTelemetry.Instrumentation.GrpcNetClient
OpenTelemetry.Instrumentation.Http
OpenTelemetry.Instrumentation.SqlClient
OpenTelemetry.Shims.OpenTracing
1.4.0-rc.1
1.4.0-rc.1
OpenTelemetry
Added dependency injection support in the
ResourceBuilderclass and addedsupport for loading environment variables from
IConfigurationfor theAddEnvironmentVariableDetectorextension (Logs)(#3889)
Refactored
AddInstrumentation,ConfigureServicesandConfigureBuilderAPIs into the OpenTelemetry.Extensions.DependencyInjection package and added
the
IServiceCollection.AddOpenTelemetryAPI(#3923)
Removed
ConfigureResourceonOpenTelemetryLoggingOptions(#3999)
OpenTelemetry.Api
7.0.0.OpenTelemetry.Exporter.Console
ActivityLinkwithout Tags.(#3932)
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
OpenTelemetry.Exporter.OpenTelemetryProtocol
OTEL_ATTRIBUTE_COUNT_LIMIT,OTEL_ATTRIBUTE_COUNT_LIMIT,OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT,OTEL_SPAN_EVENT_COUNT_LIMIT,OTEL_SPAN_LINK_COUNT_LIMIT,OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT,OTEL_LINK_ATTRIBUTE_COUNT_LIMIT. All of them are defaulted to128.(#3978)
OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs
OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.Exporter.Zipkin
OpenTelemetry.Extensions.DependencyInjection
... (truncated)
1.4.0-beta.3
1.4.0-beta.3
OpenTelemetry
Fix instrument naming enforcement implementation to match the spec.
(#3821)
Added support for loading environment variables from
IConfigurationwhenusing the
MetricReaderOptions&BatchExportActivityProcessorOptionsclasses.
(#3760,
#3776)
Added dependency injection support in the
ResourceBuilderclass and addedsupport for loading environment variables from
IConfigurationfor theAddEnvironmentVariableDetectorextension(#3782,
#3798)
Breaking: MetricPoint API to retrieve Histogram Min, Max changed. The existing
pattern of checking if Min/Max is available with
HasMinMax()and thenretrieving the same using
GetHistogramMin(),GetHistogramMax()is replacedwith a single API
TryGetHistogramMinMaxValues(out double min, out double max).(#3822)
OpenTelemetry.Api
7.0.0-rc.2.22472.3.OpenTelemetry.Exporter.Console
System.Text.Jsonto 4.7.2 in responseto CVE-2021-26701.
(#3789)
LogRecordExporter to print full exception details instead of just Message, when
using
ILoggerto log exception.(#3784)
Added support to print Histogram Min, Max in MetricExporter.
OpenTelemetry.Exporter.InMemory
OpenTelemetry.Exporter.Jaeger
System.Text.Jsonto 4.7.2 in responseto CVE-2021-26701.
(#3789)
... (truncated)
1.4.0-beta.2
1.4.0-beta.2
OpenTelemetry
Make recording of
MinandMaxfor histograms configurable, enabled bydefault.
(#2735)
Changed default bucket boundaries for Explicit Bucket Histogram from [0, 5,
10, 25, 50, 75, 100, 250, 500, 1000] to [0, 5, 10, 25, 50, 75, 100, 250, 500,
750, 1000, 2500, 5000, 7500, 10000].
(#3722)
Fixed an issue where
LogRecord.ForEachScopemay return scopes from aprevious lo...
Description has been truncated