The attributes described in this section are not specific to a particular operation but rather generic. They may be used in any Span they apply to. Particular operations may refer to or require some of these attributes.
General network connection attributes
These attributes may be used for any network related operation.
net.peer.* attributes describe properties of the remote end of the network connection
(usually the transport-layer peer, e.g. the node to which a TCP connection was established),
net.host.* properties describe the local end.
In an ideal situation, not accounting for proxies, multiple IP addresses or host names,
net.peer.* properties of a client are equal to the
net.host.* properties of the server and vice versa.
Network transport attributes
|string||Transport protocol used. See note below.||No|
|string||Remote address of the peer (dotted decimal for IPv4 or RFC5952 for IPv6)||No|
|int||Remote port number.||No|
|string||Remote hostname or similar, see note below. ||No|
|string||Local hostname or similar, see note below.||No|
|string||The internet connection type currently being used by the host.||No|
|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.||No|
|string||The name of the mobile carrier.||No|
|string||The mobile carrier country code.||No|
|string||The mobile carrier network code.||No|
|string||The ISO 3166-1 alpha-2 2-character country code associated with the mobile carrier network.||No|
net.peer.name SHOULD NOT be set if capturing it would require an extra DNS lookup.
net.transport MUST be one of the following:
|Another IP-based protocol|
|Unix Domain socket. See below.|
|Named or anonymous pipe. See note below.|
|In-process communication. |
|Something else (non IP-based).|
: 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.
net.host.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.
net.host.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.
|EVDO Rel. 0|
|EVDO Rev. A|
|EVDO Rev. B|
|5G NR (New Radio)|
|5G NRNSA (New Radio Non-Standalone)|
pipe, since the connection goes over the file system instead of being directly to a known peer,
net.peer.name is the only attribute that usually makes sense (see description of
For IP-based communication, the name should be a DNS host name.
net.peer.name, this should be the name that was used to look up the IP address that was connected to
net.peer.ip if that one is set; e.g.,
"example.com" if connecting to an URL
If only the IP address but no host name is available, reverse DNS lookup SHOULD NOT be used to obtain
net.peer.name SHOULD NOT be set.
net.host.name should be the host name of the local host,
preferably the one that the peer used to connect for the current operation.
If that is not known, a public hostname should be preferred over a private one. However, in that case it may be redundant with information already contained in resources and may be left out.
It will usually not make sense to use reverse-lookup to obtain
net.host.name, as that would result in static information that is better stored as resource information.
"pipe", the absolute path to the file representing it should be used as
net.host.name doesn’t make sense in that context).
If there is no such file (e.g., anonymous pipe),
the name should explicitly be set to the empty string to distinguish it from the case where the name is just unknown or not covered by the instrumentation.
General remote service attributes
This attribute may be used for any operation that accesses some remote service. Users can define what the name of a service is based on their particular semantics in their distributed system. Instrumentations SHOULD provide a way for users to configure this name.
peer.service that users may specify:
- A Redis cache of auth tokens as
- A gRPC service
rpc.service="io.opentelemetry.AuthService"may be hosted in both a gateway,
peer.service="ExternalApiService"and a backend,
General identity attributes
These attributes may be used for any operation with an authenticated and/or authorized enduser.
|string||Username or client_id extracted from the access token or Authorization header in the inbound request from outside the system.||No|
|string||Actual/assumed role the client is making the request under extracted from token or application security context.||No|
|string||Scopes or granted authorities the client currently possesses extracted from token or application security context. The value would come from the scope associated with an OAuth 2.0 Access Token or an attribute value in a SAML 2.0 Assertion.||No|
These attributes describe the authenticated user driving the user agent making requests to the instrumented system. It is expected this information would be propagated unchanged from node-to-node within the system using the Baggage mechanism. These attributes should not be used to record system-to-system authentication attributes.
Examples of where the
enduser.id value is extracted from:
|Authentication protocol||Field or description|
|HTTP Basic/Digest Authentication|
|OAuth 2.0 Bearer Token||OAuth 2.0 Client Identifier value from |
|OpenID Connect 1.0 IDToken|
|SAML 2.0 Assertion|
|Framework||Field or description|
|Windows Communication Foundation|
Given the sensitive nature of this information, SDKs and exporters SHOULD drop these attributes by default and then provide a configuration parameter to turn on retention for use cases where the information is required and would not violate any policies or regulations.
General thread attributes
These attributes may be used for any operation to store information about a thread that started a span.
|int||Current “managed” thread ID (as opposed to OS thread ID).||No|
|string||Current thread name.||No|
Examples of where
thread.name can be extracted from:
|Language or platform|
Source Code Attributes
Often a span is closely tied to a certain unit of code that is logically responsible for handling the operation that the span describes (usually the method that starts the span). For an HTTP server span, this would be the function that handles the incoming request, for example. The attributes listed below allow to report this unit of code and therefore to provide more context about the span.
|string||The method or function name, or equivalent (usually rightmost part of the code unit’s name).||No|
|string||The “namespace” within which ||No|
|string||The source code file name that identifies the code unit as uniquely as possible (preferably an absolute file path).||No|
|int||The line number in ||No|