Context
This issue is a follow-up to https://github.com/open-telemetry/semantic-conventions/pull/89/files#r1299769832. We need to take the opportunity of the attribute renaming required for #51 and choose names that inspire full confidence. The goal is to open a discussion and reach consensus on attribute names that minimize the risk of future changes.
All Network Metrics Attributes (Old Name / Current Name):
device -> system.device
direction -> system.network.direction
protocol -> network.protocol
state -> system.network.state
We should revisit each of these attributes within the scope of this issue. If you have any ideas or suggestions, please comment. The following are the main concerns we should address:
protocol / network.protocol
We picked network.protocol because it's generic and can be applicable to other metrics. It's listed in https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md#network-attributes. We should rename it to network.protocol.name then.
state / system.network.state
While it currently sounds like a state of the network, in the OTel collector host metrics receiver, it represents connection status (e.g., "CLOSED," "LISTEN," ESTABLISHED," etc.). I think we should rename it to network.connection.status and add it to https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md#network-attributes.
Sub-issues (added by @mx-psi):
Context
This issue is a follow-up to https://github.com/open-telemetry/semantic-conventions/pull/89/files#r1299769832. We need to take the opportunity of the attribute renaming required for #51 and choose names that inspire full confidence. The goal is to open a discussion and reach consensus on attribute names that minimize the risk of future changes.
All Network Metrics Attributes (Old Name / Current Name):
device->system.devicedirection->system.network.directionprotocol->network.protocolstate->system.network.stateWe should revisit each of these attributes within the scope of this issue. If you have any ideas or suggestions, please comment. The following are the main concerns we should address:
protocol/network.protocolWe picked
network.protocolbecause it's generic and can be applicable to other metrics. It's listed in https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md#network-attributes. We should rename it tonetwork.protocol.namethen.state/system.network.stateWhile it currently sounds like a state of the network, in the OTel collector host metrics receiver, it represents connection status (e.g., "CLOSED," "LISTEN," ESTABLISHED," etc.). I think we should rename it to
network.connection.statusand add it to https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/attributes.md#network-attributes.Sub-issues (added by @mx-psi):
devicetosystem.devicenetwork.interface.namedirectiontosystem.network.directionnetwork.io.directionwith valuestransmit/receiveprotocoltonetwork.protocolornetwork.protocol.namenetwork.protocol.namestatetosystem.network.statesystem.cpu.logical_numbertohost.cpu.logical_number