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
I'm not sure that knowing ipv4 vs ipv6 is a generally useful piece of data in the scope of HTTP semconv (worth capturing by default on all HTTP spans).
Should we remove it, or explicitly make it opt-in?
The text was updated successfully, but these errors were encountered:
Assuming the backend does not want to parse the IP address it does not need the type. It's still obvious (on traces) if the network.peer.address is IPv4 or IPv6. Even if instrumentations don't populate it, backends MAY figure out the type.
But metrics are more interesting: I assume it might be interesting how much traffic is coming over ipv4 vs ipv6.
I'd be in favor of keeping it on traces, adding to metrics, and making it opt-in on both.
trask
changed the title
Remove network.type from HTTP semconv, or explicitly make it opt-in?
Make network.type opt-in for HTTP semconv spans and metrics?
Oct 16, 2023
I'm not sure that knowing
ipv4
vsipv6
is a generally useful piece of data in the scope of HTTP semconv (worth capturing by default on all HTTP spans).Should we remove it, or explicitly make it opt-in?
The text was updated successfully, but these errors were encountered: