Network

These attributes may be used for any network related operation.

Network Attributes

AttributeTypeDescriptionExamplesStability
network.carrier.iccstringThe ISO 3166-1 alpha-2 2-character country code associated with the mobile carrier network.DEExperimental
network.carrier.mccstringThe mobile carrier country code.310Experimental
network.carrier.mncstringThe mobile carrier network code.001Experimental
network.carrier.namestringThe name of the mobile carrier.sprintExperimental
network.connection.subtypestringThis describes more details regarding the connection.type. It may be the type of cell technology connection, but it could be used for describing details about a wifi connection.LTEExperimental
network.connection.typestringThe internet connection type.wifiExperimental
network.io.directionstringThe network IO operation direction.transmitExperimental
network.local.addressstringLocal address of the network connection - IP address or Unix domain socket name.10.1.2.80; /tmp/my.sockStable
network.local.portintLocal port number of the network connection.65123Stable
network.peer.addressstringPeer address of the network connection - IP address or Unix domain socket name.10.1.2.80; /tmp/my.sockStable
network.peer.portintPeer port number of the network connection.65123Stable
network.protocol.namestringOSI application layer or non-OSI equivalent. [1]amqp; http; mqttStable
network.protocol.versionstringThe actual version of the protocol used for network communication. [2]1.1; 2Stable
network.transportstringOSI transport layer or inter-process communication method. [3]tcp; udpStable
network.typestringOSI network layer or non-OSI equivalent. [4]ipv4; ipv6Stable

[1]: The value SHOULD be normalized to lowercase.

[2]: If protocol version is subject to negotiation (for example using ALPN), this attribute SHOULD be set to the negotiated version. If the actual protocol version is not known, this attribute SHOULD NOT be set.

[3]: The value SHOULD be normalized to lowercase.

Consider always setting the transport when setting a port number, since a port number is ambiguous without knowing the transport. For example different processes could be listening on TCP port 12345 and UDP port 12345.

[4]: The value SHOULD be normalized to lowercase.

network.connection.subtype has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
gprsGPRSExperimental
edgeEDGEExperimental
umtsUMTSExperimental
cdmaCDMAExperimental
evdo_0EVDO Rel. 0Experimental
evdo_aEVDO Rev. AExperimental
cdma2000_1xrttCDMA2000 1XRTTExperimental
hsdpaHSDPAExperimental
hsupaHSUPAExperimental
hspaHSPAExperimental
idenIDENExperimental
evdo_bEVDO Rev. BExperimental
lteLTEExperimental
ehrpdEHRPDExperimental
hspapHSPAPExperimental
gsmGSMExperimental
td_scdmaTD-SCDMAExperimental
iwlanIWLANExperimental
nr5G NR (New Radio)Experimental
nrnsa5G NRNSA (New Radio Non-Standalone)Experimental
lte_caLTE CAExperimental

network.connection.type has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
wifiwifiExperimental
wiredwiredExperimental
cellcellExperimental
unavailableunavailableExperimental
unknownunknownExperimental

network.io.direction MUST be one of the following:

ValueDescriptionStability
transmittransmitExperimental
receivereceiveExperimental

network.transport has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
tcpTCPStable
udpUDPStable
pipeNamed or anonymous pipe.Stable
unixUnix domain socketStable

network.type has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
ipv4IPv4Stable
ipv6IPv6Stable

Deprecated Network Attributes

AttributeTypeDescriptionExamplesStability
net.host.namestringDeprecated, use server.address.example.comDeprecated
Replaced by server.address.
net.host.portintDeprecated, use server.port.8080Deprecated
Replaced by server.port.
net.peer.namestringDeprecated, use server.address on client spans and client.address on server spans.example.comDeprecated
Replaced by server.address on client spans and client.address on server spans.
net.peer.portintDeprecated, use server.port on client spans and client.port on server spans.8080Deprecated
Replaced by server.port on client spans and client.port on server spans.
net.protocol.namestringDeprecated, use network.protocol.name.amqp; http; mqttDeprecated
Replaced by network.protocol.name.
net.protocol.versionstringDeprecated, use network.protocol.version.3.1.1Deprecated
Replaced by network.protocol.version.
net.sock.familystringDeprecated, use network.transport and network.type.inetDeprecated
Split to network.transport and network.type.
net.sock.host.addrstringDeprecated, use network.local.address./var/my.sockDeprecated
Replaced by network.local.address.
net.sock.host.portintDeprecated, use network.local.port.8080Deprecated
Replaced by network.local.port.
net.sock.peer.addrstringDeprecated, use network.peer.address.192.168.0.1Deprecated
Replaced by network.peer.address.
net.sock.peer.namestringDeprecated, no replacement at this time./var/my.sockDeprecated
Removed.
net.sock.peer.portintDeprecated, use network.peer.port.65531Deprecated
Replaced by network.peer.port.
net.transportstringDeprecated, use network.transport.ip_tcpDeprecated
Replaced by network.transport.

net.sock.family has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
inetIPv4 addressExperimental
inet6IPv6 addressExperimental
unixUnix domain socket pathExperimental

net.transport has the following list of well-known values. If one of them applies, then the respective value MUST be used; otherwise, a custom value MAY be used.

ValueDescriptionStability
ip_tcpip_tcpExperimental
ip_udpip_udpExperimental
pipeNamed or anonymous pipe.Experimental
inprocIn-process communication. [1]Experimental
otherSomething else (non IP-based).Experimental

[1]: Signals that there is only in-process communication not using a “real” network protocol in cases where network attributes would normally be expected. Usually all other network attributes can be left out in that case.