-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Open
hyperium/hyper-util
#145Labels
A-clientArea: client.Area: client.C-featureCategory: feature. This is adding a new feature.Category: feature. This is adding a new feature.E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.Effort: medium. Some knowledge of how hyper internal works would be useful.K-hyper-utilCrate: hyper-utilCrate: hyper-util
Description
Is your feature request related to a problem? Please describe.
While investigating hard-to-debug connection related issues in cloud infra, we will likely want to obtain any kind of information that might be relevant. Even whether a connection that has just failed is reused from the connection pool or is newly established can be a valuable insight that we could use to troubleshoot.
Describe the solution you'd like
Maybe add a new private field to the hyper_util::client::legacy::connect::HttpInfo
, like is_new_connection
(or is_reused_connection
) and make it publicly accessible via a method?
Describe alternatives you've considered
I didn't come up with other alternatives
Additional context
N/A
Metadata
Metadata
Assignees
Labels
A-clientArea: client.Area: client.C-featureCategory: feature. This is adding a new feature.Category: feature. This is adding a new feature.E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.Effort: medium. Some knowledge of how hyper internal works would be useful.K-hyper-utilCrate: hyper-utilCrate: hyper-util