Skip to content

Implement the Metrics counterpart of System.Net EventCounters #88383

Open
@antonfirsov

Description

@antonfirsov

Opening a separate issue for System.Net.NameResolution/Security/Socket specific parts of #79371. We should implement the Metrics counterpart of the events listed below.

I wasn't able to find any OTel specifications for this area, which would require us to change the semantics, so my assumption is that this should be fairly trivial work.

It might complicate things if we want to enable passing an IMeterFactory to Dns or Socket similarly to #86961, but that work can be done incrementally.

System.Net.NameResolution

All counters listed in https://learn.microsoft.com/en-us/dotnet/core/diagnostics/available-counters#systemnetnameresolution-counters

  • dns-lookups-requested
  • dns-lookups-duration
  • current-dns-lookups

Also tracked in #48885.

System.Net.Security

All counters listed in https://learn.microsoft.com/en-us/dotnet/core/diagnostics/available-counters#systemnetsecurity-counters:

  • tls-handshake-rate
  • total-tls-handshakes
  • current-tls-handshakes
  • failed-tls-handshakes
  • all-tls-sessions-open
  • tls10-sessions-open
  • tls11-sessions-open
  • tls12-sessions-open
  • tls13-sessions-open
  • all-tls-handshake-duration
  • tls10-handshake-duration
  • tls11-handshake-duration
  • tls12-handshake-duration
  • tls13-handshake-duration

System.Net.Sockets

All counters listed in https://learn.microsoft.com/en-us/dotnet/core/diagnostics/available-counters#systemnetsockets-counters

  • outgoing-connections-established
  • incoming-connections-established
  • current-outgoing-connect-attempts
  • bytes-received
  • bytes-sent
  • datagrams-received
  • datagrams-sent

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions