Kestrel connection metrics - add protocol and TLS info?

[JamesNK]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Kestrel has a connection-duration counter. Today it just records the local endpoint as a dimension.

Describe the solution you'd like

connection-duration could add additional information that is negotiated after the connection starts.

For example, the connection's:

• HTTP protocol (HTTP/1.1, HTTP/2, HTTP/3)
• TLS protocol (Tls10, Tls11, Tls12, Tls13)

Is this valuable?

Additional context

No response

[gfoidl]

For me:
HTTP protocol: yes
TLS protocol: not needed

Also need to consider that the curse of dimensionality doesn't start to account 😉.

[amcasey]

How is the data structured? Is there a side table for tracking metadata about each endpoint or does everything go on every event?

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.