Improve the definition of state
#2623
Assignees
Labels
area:semantic-conventions
Related to semantic conventions
enhancement
New feature or request
spec:metrics
Related to the specification/metrics directory
triaged-accepted
The issue is triaged and accepted by the OTel community, one can proceed with creating a PR proposal
Comments
arminru
added
area:semantic-conventions
reyang
added
the
triaged-accepted
|
This a good suggestion. Thank you for the recommendation. It is accepted. |
codeboten
pushed a commit
to codeboten/opentelemetry-specification
that referenced
this issue
Jul 14, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are you trying to achieve?
Currently the definition for the
stateattribute of thesystem.network.connectionsmetric really only applies to TCP connections. It should either be defined in a way that makes it meaningful to multiple protocols or the metric should be separated per protocol.Additional context.
This issue is a follow up to the discussion here: #2617 (comment)
The text was updated successfully, but these errors were encountered: