We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
system.network.connections
What are you trying to achieve?
Since UDP has no state, I propose UDP and TCP connection metrics should be split into protocol specific metric for each supported protocol.
If folks agree, I will open a PR to mark system.network.connections as deprecated in favour of:
system.network.tcp.connections system.network.udp.connections
system.network.tcp.connections
system.network.udp.connections
Additional context.
The work for this was previously done in open-telemetry/opentelemetry-specification#2675 and reverted in open-telemetry/opentelemetry-specification#2748. See open-telemetry/opentelemetry-specification#2726 for additional context
The text was updated successfully, but these errors were encountered:
@jsuereth Can we transfer this to the semantic-conventions repository?
Sorry, something went wrong.
@codeboten, is this still applicable after the revert is done in open-telemetry/opentelemetry-specification#2726? Can we close it now?
@codeboten Can you help us with the question above?
With the recommendation to not set the state attribute for stateless protocols, this is probably ok to close
state
codeboten
reyang
No branches or pull requests
What are you trying to achieve?
Since UDP has no state, I propose UDP and TCP connection metrics should be split into protocol specific metric for each supported protocol.
If folks agree, I will open a PR to mark system.network.connections as deprecated in favour of:
system.network.tcp.connections
system.network.udp.connections
Additional context.
The work for this was previously done in open-telemetry/opentelemetry-specification#2675 and reverted in open-telemetry/opentelemetry-specification#2748. See open-telemetry/opentelemetry-specification#2726 for additional context
The text was updated successfully, but these errors were encountered: