1.6.0-beta.2 #4996
utpilla
announced in
Announcements
1.6.0-beta.2
#4996
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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.
NOTES:
.NET8.0framework or newer,http.server.request.durationmetric will only follow v1.22.0 semantic conventions specification. Ability to switch behavior to older conventions usingOTEL_SEMCONV_STABILITY_OPT_INenvironment variable is not available.(#4934)
Added
network.protocol.namedimension tohttp.server.request.durationmetric. This change only affects users settingOTEL_SEMCONV_STABILITY_OPT_INtohttporhttp/dup. (#4934)Breaking: Removed
EnrichandFiltersupport for metrics instrumentation. With this change,AspNetCoreMetricsInstrumentationOptionsis no longer available. (#4981)Enrichmigration:An enrichment API for the
http.server.request.durationmetric is available inside AspNetCore for users targeting .NET 8.0 (or newer). For details see: Enrich the ASP.NET Core requestmetric.
Filtermigration:There is no comparable filter mechanism currently available for any .NET version. Please share your feedback if you are impacted by this feature gap.
Updated description for
http.server.request.durationmetrics to match spec definition. (#4990)OpenTelemetry.Instrumentation.Http
HttpClient,http.client.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). (#4870)http.client.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.client.durationms(milliseconds)0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000Note: The older
http.client.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:http-spans
http-metrics
Added support for publishing
http.client.duration&http.client.request.durationmetrics on .NET Framework forHttpWebRequest. (#4870)Following
HttpClientmetrics will now be enabled by default when targeting.NET8.0framework or newer.Meter :
System.Net.Httphttp.client.request.durationhttp.client.active_requestshttp.client.open_connectionshttp.client.connection.durationhttp.client.request.time_in_queueMeter :
System.Net.NameResolutiondns.lookups.durationFor details about each individual metric check System.Net metrics docs page.
NOTES:
.NET8.0framework or newer,http.client.request.durationmetric will only follow v1.22.0 semantic conventions specification. Ability to switch behavior to older conventions usingOTEL_SEMCONV_STABILITY_OPT_INenvironment variable isnot available.
(#4931)
Added
url.schemeattribute tohttp.client.request.durationmetric. The metric will be emitted whenOTEL_SEMCONV_STABILITY_OPT_INenvironment variable is set tohttporhttp/dup. (#4989)Updated description for
http.client.request.durationmetrics to match spec definition. (#4990)This discussion was created from the release 1.6.0-beta.2.
Beta Was this translation helpful? Give feedback.
All reactions