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
-
OpenTelemetry.Instrumentation.AspNetCore
http.server.request.duration
measured 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_IN
environment variable to eitherhttp
(to emit only the new metric) orhttp/dup
(to emit both the new and old metrics). (#4802)http.server.request.duration
s
(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, 10
http.server.duration
ms
(milliseconds)0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000
Note: the older
http.server.duration
metric andOTEL_SEMCONV_STABILITY_OPT_IN
environment 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.0
or newer framework:Meter :
Microsoft.AspNetCore.Hosting
http.server.request.duration
http.server.active_requests
Meter :
Microsoft.AspNetCore.Server.Kestrel
kestrel.active_connections
kestrel.connection.duration
kestrel.rejected_connections
kestrel.queued_connections
kestrel.queued_requests
kestrel.upgraded_connections
kestrel.tls_handshake.duration
kestrel.active_tls_handshakes
Meter :
Microsoft.AspNetCore.Http.Connections
signalr.server.connection.duration
signalr.server.active_connections
Meter :
Microsoft.AspNetCore.Routing
aspnetcore.routing.match_attempts
Meter :
Microsoft.AspNetCore.Diagnostics
aspnetcore.diagnostics.exceptions
Meter :
Microsoft.AspNetCore.RateLimiting
aspnetcore.rate_limiting.active_request_leases
aspnetcore.rate_limiting.request_lease.duration
aspnetcore.rate_limiting.queued_requests
aspnetcore.rate_limiting.request.time_in_queue
aspnetcore.rate_limiting.requests
For details about each individual metric check ASP.NET Core docs page.
NOTES:
.NET8.0
framework or newer,http.server.request.duration
metric will only follow v1.22.0 semantic conventions specification. Ability to switch behavior to older conventions usingOTEL_SEMCONV_STABILITY_OPT_IN
environment variable is not available.(#4934)
Added
network.protocol.name
dimension tohttp.server.request.duration
metric. This change only affects users settingOTEL_SEMCONV_STABILITY_OPT_IN
tohttp
orhttp/dup
. (#4934)Breaking: Removed
Enrich
andFilter
support for metrics instrumentation. With this change,AspNetCoreMetricsInstrumentationOptions
is no longer available. (#4981)Enrich
migration:An enrichment API for the
http.server.request.duration
metric is available inside AspNetCore for users targeting .NET 8.0 (or newer). For details see: Enrich the ASP.NET Core requestmetric.
Filter
migration: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.duration
metrics to match spec definition. (#4990)OpenTelemetry.Instrumentation.Http
HttpClient
,http.client.request.duration
measured 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_IN
environment variable to eitherhttp
(to emit only the new metric) orhttp/dup
(to emit both the new and old metrics). (#4870)http.client.request.duration
s
(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, 10
http.client.duration
ms
(milliseconds)0, 5, 10, 25, 50, 75, 100, 250, 500, 750, 1000, 2500, 5000, 7500, 10000
Note: The older
http.client.duration
metric andOTEL_SEMCONV_STABILITY_OPT_IN
environment 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.duration
metrics on .NET Framework forHttpWebRequest
. (#4870)Following
HttpClient
metrics will now be enabled by default when targeting.NET8.0
framework or newer.Meter :
System.Net.Http
http.client.request.duration
http.client.active_requests
http.client.open_connections
http.client.connection.duration
http.client.request.time_in_queue
Meter :
System.Net.NameResolution
dns.lookups.duration
For details about each individual metric check System.Net metrics docs page.
NOTES:
.NET8.0
framework or newer,http.client.request.duration
metric will only follow v1.22.0 semantic conventions specification. Ability to switch behavior to older conventions usingOTEL_SEMCONV_STABILITY_OPT_IN
environment variable isnot available.
(#4931)
Added
url.scheme
attribute tohttp.client.request.duration
metric. The metric will be emitted whenOTEL_SEMCONV_STABILITY_OPT_IN
environment variable is set tohttp
orhttp/dup
. (#4989)Updated description for
http.client.request.duration
metrics 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