You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to enrich DNS data with client latency using TCP connections.
Describe the solution you'd like
It possible to extract data from live capture or pcap file of TCP handshake RTT values of client and report information, that basically is user latency (not server latency).
Describe alternatives you've considered
Currently I'm doing that using separate simple code I wrote using GO.
Additional context
Even though TCP connection is usually only about 6-15% of all requests this is enough sample data to make conclusion quality of your service towards specifics prefixes (with aggregation ipv4 /24 and ipv6 /48)
Is your feature request related to a problem? Please describe.
I would like to enrich DNS data with client latency using TCP connections.
Describe the solution you'd like
It possible to extract data from live capture or pcap file of TCP handshake RTT values of client and report information, that basically is user latency (not server latency).
Describe alternatives you've considered
Currently I'm doing that using separate simple code I wrote using GO.
Additional context
Even though TCP connection is usually only about 6-15% of all requests this is enough sample data to make conclusion quality of your service towards specifics prefixes (with aggregation ipv4 /24 and ipv6 /48)
This specific paper goes more into details
https://ant.isi.edu/~johnh/PAPERS/Moura20a.pdf
Here what I did for now
The text was updated successfully, but these errors were encountered: