-
Notifications
You must be signed in to change notification settings - Fork 892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add definition for state attribute of system.network.connections #2663
Conversation
Replacing wikipedia link with set values for the state. I would add that the states listed here only apply to TCP protocol, which reinforces my thinking that the system.network.connections metric should be split by protocol. Asking reviewers to consider this. If folks agree, I will open a follow up PR to mark `system.network.connections` as deprecated in favour of `system.network.tcp.connections` and `system.network.udp.connections`. Fixes open-telemetry#2623
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
The semantics introduced by this PR allowing to distinguish TCP and UDP by the presence or absence of |
As a follow up to open-telemetry#2663, since UDP has no state attribute, I propose UDP and TCP connection metrics should be split into protocol specific metric for each supported protocol.
Fixes #2623
Changes
Replacing wikipedia link with set values for the state. I would add that the states listed here only apply to TCP protocol, which reinforces my thinking that the system.network.connections metric should be split by protocol. Asking reviewers to consider this.
If folks agree, I will open a follow up PR to mark
system.network.connections
as deprecated in favour of:system.network.tcp.connections
system.network.udp.connections