Skip to content

Adjust Networking metrics to follow OpenTelemetry semantic conventions #89093

Closed
@antonfirsov

Description

@antonfirsov

Edit: for folks landing on this issue, I'm linking the final spec of the Metrics implemented in .NET 8.0: https://github.com/lmolkova/semantic-conventions/blob/dotnet8-metrics/docs/dotnet/README.md


We are implementing the following metrics for .NET 8 with ad-hoc naming:

// Request metrics:
http-client-current-requests (scheme, host, port, method)
http-client-request-duration (scheme, host, port, method, status-code, protocol)
http-client-failed-requests  (scheme, host, port, method, status-code, protocol)

// Connection metrics:
http-client-current-connections      (protocol, scheme, host, port)
http-client-current-idle-connections (protocol, scheme, host, port)
http-client-connection-duration      (protocol, scheme, host, port)

// How long is a request waiting in the connection pool's queue:
http-client-requests-queue-duration  (protocol, scheme, host, port)

dns-lookups-requested(hostname)

We need to adjust these instruments to follow OpenTelemetry semantic conventions in naming and other aspects. Details TBD.

Metadata

Metadata

Assignees

Labels

area-System.NetenhancementProduct code improvement that does NOT require public API changes/additions

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions