Network

These attributes may be used for any network related operation.

Network Attributes

Attribute	Type	Description	Examples
network.carrier.icc	string	The ISO 3166-1 alpha-2 2-character country code associated with the mobile carrier network.	DE
network.carrier.mcc	string	The mobile carrier country code.	310
network.carrier.mnc	string	The mobile carrier network code.	001
network.carrier.name	string	The name of the mobile carrier.	sprint
network.connection.subtype	string	This 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.	LTE
network.connection.type	string	The internet connection type.	wifi
network.io.direction	string	The network IO operation direction.	transmit
network.local.address	string	Local address of the network connection - IP address or Unix domain socket name.	10.1.2.80; /tmp/my.sock
network.local.port	int	Local port number of the network connection.	65123
network.peer.address	string	Peer address of the network connection - IP address or Unix domain socket name.	10.1.2.80; /tmp/my.sock
network.peer.port	int	Peer port number of the network connection.	65123
network.protocol.name	string	OSI application layer or non-OSI equivalent. [1]	amqp; http; mqtt
network.protocol.version	string	Version of the protocol specified in network.protocol.name. [2]	3.1.1
network.transport	string	OSI transport layer or inter-process communication method. [3]	tcp; udp
network.type	string	OSI network layer or non-OSI equivalent. [4]	ipv4; ipv6

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

[2]: network.protocol.version refers to the version of the protocol used and might be different from the protocol client’s version. If the HTTP client has a version of 0.27.2, but sends HTTP version 1.1, this attribute should be set to 1.1.

[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.

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.

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

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.

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.

Deprecated Network Attributes

Attribute	Type	Description	Examples
net.host.name	string	Deprecated, use server.address.	example.com
net.host.port	int	Deprecated, use server.port.	8080
net.peer.name	string	Deprecated, use server.address on client spans and client.address on server spans.	example.com
net.peer.port	int	Deprecated, use server.port on client spans and client.port on server spans.	8080
net.protocol.name	string	Deprecated, use network.protocol.name.	amqp; http; mqtt
net.protocol.version	string	Deprecated, use network.protocol.version.	3.1.1
net.sock.family	string	Deprecated, use network.transport and network.type.	inet
net.sock.host.addr	string	Deprecated, use network.local.address.	/var/my.sock
net.sock.host.port	int	Deprecated, use network.local.port.	8080
net.sock.peer.addr	string	Deprecated, use network.peer.address.	192.168.0.1
net.sock.peer.name	string	Deprecated, no replacement at this time.	/var/my.sock
net.sock.peer.port	int	Deprecated, use network.peer.port.	65531
net.transport	string	Deprecated, use network.transport.	ip_tcp

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.

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.

[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.