ResourceAttributes

The Amazon Resource Name(s) (ARN) of the AWS log group(s).

Notes: - See the <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/iam-access-control-overview-cwl.html#CWL_ARN_Format">log group ARN format documentation.

The name(s) of the AWS log group(s) an application is writing to.

Notes: - Multiple log groups must be supported for cases like multi-container applications, where a single application has sidecar containers, and each write to their own log group.

The ARN(s) of the AWS log stream(s).

Notes: - See the <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/iam-access-control-overview-cwl.html#CWL_ARN_Format">log stream ARN format documentation. One log group can contain several log streams, so these ARNs necessarily identify both a log group and a log stream.

Array of brand name and version separated by a space

Notes: - This value is intended to be taken from the <a href="https://wicg.github.io/ua-client-hints/#interface">UA client hints API (`navigator.userAgentData.brands`).

Preferred language of the user using the browser

Notes: - This value is intended to be taken from the Navigator API navigator.language.

A boolean that is true if the browser is running on a mobile device

Notes: - This value is intended to be taken from the <a href="https://wicg.github.io/ua-client-hints/#interface">UA client hints API (`navigator.userAgentData.mobile`). If unavailable, this attribute SHOULD be left unset.

The platform on which the browser is running

Notes: - This value is intended to be taken from the <a href="https://wicg.github.io/ua-client-hints/#interface">UA client hints API (`navigator.userAgentData.platform`). If unavailable, the legacy `navigator.platform` API SHOULD NOT be used instead and this attribute SHOULD be left unset in order for the values to be consistent. The list of possible values is defined in the W3C User-Agent Client Hints specification. Note that some (but not all) of these values can overlap with values in the `os.type` and `os.name` attributes. However, for consistency, the values in the browser.platform attribute should capture the exact value that the user agent provides.

Cloud regions often have multiple, isolated locations known as zones to increase availability. Availability zone represents the zone where the resource is running.

Notes: - Availability zones are called "zones" on Alibaba Cloud and Google Cloud.

The cloud platform in use.

Notes: - The prefix of the service SHOULD match the one specified in cloud.provider.

The geographical region the resource is running.

Notes: - Refer to your provider's docs to see the available regions, for example <a href="https://www.alibabacloud.com/help/doc-detail/40654.htm">Alibaba Cloud regions, AWS regions, <a href="https://azure.microsoft.com/global-infrastructure/geographies/">Azure regions, Google Cloud regions, or Tencent Cloud regions.

The command used to run the container (i.e. the command name).

Notes: - If using embedded credentials or sensitive data, it is recommended to remove them to prevent potential leakage.

Runtime specific image identifier. Usually a hash algorithm followed by a UUID.

Notes: - Docker defines a sha256 of the image id; container.image.id corresponds to the Image field from the Docker container inspect <a href="https://docs.docker.com/engine/api/v1.43/#tag/Container/operation/ContainerInspect">API endpoint. K8s defines a link to the container registry repository with digest `"imageID": "registry.azurecr.io /namespace/service/dockerfile@sha256:bdeabd40c3a8a492eaf9e8e44d0ebbb84bac7ee25ac0cf8a7159d25f62555625"`. The ID is assinged by the container runtime and can vary in different environments. Consider using `oci.manifest.digest` if it is important to identify the same image in different environments/runtimes.

Repo digests of the container image as provided by the container runtime.

Notes: - <a href="https://docs.docker.com/engine/api/v1.43/#tag/Image/operation/ImageInspect">Docker and CRI report those under the RepoDigests field.

A unique identifier representing the device

Notes: - The device identifier MUST only be defined using the values outlined below. This value is not an advertising identifier and MUST NOT be used as such. On iOS (Swift or Objective-C), this value MUST be equal to the <a href="https://developer.apple.com/documentation/uikit/uidevice/1620059-identifierforvendor">vendor identifier. On Android (Java or Kotlin), this value MUST be equal to the Firebase Installation ID or a globally unique UUID which is persisted across sessions in your application. More information can be found here on best practices and exact implementation details. Caution should be taken when storing personal data or anything which can identify a user. GDPR and data protection laws may apply, ensure you do your own due diligence.

The name of the device manufacturer

Notes: - The Android OS provides this field via <a href="https://developer.android.com/reference/android/os/Build#MANUFACTURER">Build. iOS apps SHOULD hardcode the value `Apple`.

The model identifier for the device

Notes: - It's recommended this value represents a machine readable version of the model identifier rather than the market or consumer-friendly name of the device.

The marketing name for the device model

Notes: - It's recommended this value represents a human readable version of the device model rather than a machine readable alternative.

The execution environment ID as a string, that will be potentially reused for other invocations to the same function/function version.

Notes: - AWS Lambda: Use the (full) log stream name.

The amount of memory available to the serverless function converted to Bytes.

Notes: - It's recommended to set this attribute since e.g. too little memory can easily stop a Java AWS Lambda function from working correctly. On AWS Lambda, the environment variable AWS_LAMBDA_FUNCTION_MEMORY_SIZE provides this information (which must be multiplied by 1,048,576).

The name of the single function that this runtime instance executes.

Notes: - This is the name of the function as configured/deployed on the FaaS platform and is usually different from the name of the callback function (which may be stored in the <a href="/docs/general/attributes.md#source-code-attributes">code.namespace/code.function span attributes). - For some cloud providers, the above definition is ambiguous. The following definition of function name MUST be used for this attribute (and consequently the span name) for the listed cloud providers/products: - Azure: The full name ` / `, i.e., function app name followed by a forward slash followed by the function name (this form can also be seen in the resource JSON for the function). This means that a span attribute MUST be used, as an Azure function app can host multiple functions that would usually share a TracerProvider (see also the `cloud.resource_id` attribute).

The immutable version of the function being executed.

Notes: - Depending on the cloud provider and platform, use: - AWS Lambda: The <a href="https://docs.aws.amazon.com/lambda/latest/dg/configuration-versions.html">function version (an integer represented as a decimal string). - Google Cloud Run (Services): The revision (i.e., the function name plus the revision suffix).

- Google Cloud Functions: The value of the <a href="https://cloud.google.com/functions/docs/env-var#runtime_environment_variables_set_automatically">K_REVISION environment variable. - Azure Functions: Not applicable. Do not set this attribute.

Processor manufacturer identifier. A maximum 12-character string.

Notes: - CPUID command returns the vendor ID string in EBX, EDX and ECX registers. Writing these to memory in this order results in a 12-character string.

Available IP addresses of the host, excluding loopback interfaces.

Notes: - IPv4 Addresses MUST be specified in dotted-quad notation. IPv6 addresses MUST be specified in the <a href="https://www.rfc-editor.org/rfc/rfc5952.html">RFC 5952 format.

Available MAC addresses of the host, excluding loopback interfaces.

Notes: - MAC Addresses MUST be represented in <a href="https://standards.ieee.org/wp-content/uploads/import/documents/tutorials/eui.pdf">IEEE RA hexadecimal form: as hyphen-separated octets in uppercase hexadecimal form from most to least significant.

A pseudo-ID for the cluster, set to the UID of the kube-system namespace.

Notes: - K8s doesn't have support for obtaining a cluster ID. If this is ever added, we will recommend collecting the k8s.cluster.uid through the official APIs. In the meantime, we are able to use the uid of the kube-system namespace as a proxy for cluster ID. Read on for the rationale. - Every object created in a K8s cluster is assigned a distinct UID. The kube-system namespace is used by Kubernetes itself and will exist for the lifetime of the cluster. Using the uid of the kube-system namespace is a reasonable proxy for the K8s ClusterID as it will only change if the cluster is rebuilt. Furthermore, Kubernetes UIDs are UUIDs as standardized by <a href="https://www.itu.int/ITU-T/studygroups/com17/oid.html">ISO/IEC 9834-8 and ITU-T X.667. Which states:

- If generated according to one of the mechanisms defined in Rec.

The digest of the OCI image manifest. For container images specifically is the digest by which the container image is known.

Notes: - Follows <a href="https://github.com/opencontainers/image-spec/blob/main/manifest.md">OCI Image Manifest Specification, and specifically the Digest property. An example can be found in <a href="https://docs.docker.com/registry/spec/manifest-v2-2/#example-image-manifest">Example Image Manifest.

The string ID of the service instance.

Notes: - MUST be unique for each instance of the same service.namespace,service.name pair (in other words service.namespace,service.name,service.instance.id triplet MUST be globally unique). The ID helps to distinguish instances of the same service that exist at the same time (e.g. instances of a horizontally scaled service). It is preferable for the ID to be persistent and stay the same for the lifetime of the service instance, however it is acceptable that the ID is ephemeral and changes during important lifetime events for the service (e.g. service restarts). If the service has no inherent unique ID that can be used as the value of this attribute it is recommended to generate a random Version 1 or Version 4 RFC 4122 UUID (services aiming for reproducible UUIDs may also use Version 5, see RFC 4122 for more recommendations).

Logical name of the service.

Notes: - MUST be the same for all instances of horizontally scaled services. If the value was not specified, SDKs MUST fallback to unknown_service: concatenated with <a href="process.md#process">process.executable.name, e.g. `unknown_service:bash`. If `process.executable.name` is not available, the value MUST be set to `unknown_service`.

A namespace for service.name.

Notes: - A string value having a meaning that helps to distinguish a group of services, for example the team name that owns a group of services. service.name is expected to be unique within the same namespace. If service.namespace is not specified in the Resource then service.name is expected to be unique for all services that have no explicit namespace defined (so the empty/unspecified namespace is simply one more valid namespace). Zero-length namespace string is assumed equal to unspecified namespace.

The name of the auto instrumentation agent or distribution, if used.

Notes: - Official auto instrumentation agents and distributions SHOULD set the telemetry.distro.name attribute to a string starting with opentelemetry-, e.g. opentelemetry-java-instrumentation.

The name of the telemetry SDK as defined above.

Notes: - The OpenTelemetry SDK MUST set the telemetry.sdk.name attribute to opentelemetry. If another SDK, like a fork or a vendor-provided implementation, is used, this SDK MUST set the telemetry.sdk.name attribute to the fully-qualified class or module name of this SDK's main entry point or another suitable identifier depending on the language. The identifier opentelemetry is reserved and MUST NOT be used in this case. All custom identifiers SHOULD be stable across different versions of an implementation.

Full user-agent string provided by the browser

Notes:

- The user-agent value SHOULD be provided only from browsers that do not have a mechanism to retrieve brands and platform individually from the User-Agent Client Hints API. To retrieve the value, the legacy navigator.userAgent API can be used.

The unique ID of the single function that this runtime instance executes.

Notes:

- On some cloud providers, it may not be possible to determine the full ID at startup, so consider setting faas.id as a span attribute instead. - The exact value to use for faas.id depends on the cloud provider: - AWS Lambda: The function <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">ARN. Take care not to use the "invoked ARN" directly but replace any alias suffix with the resolved function version, as the same runtime instance may be invokable with multiple different aliases.

- GCP: The <a href="https://cloud.google.com/iam/docs/full-resource-names">URI of the resource - Azure: The Fully Qualified Resource ID of the invoked function, not the function app, having the form /subscriptions/<SUBSCIPTION_GUID>/resourceGroups/<RG>/providers/Microsoft.Web/sites/<FUNCAPP>/functions/<FUNC>}. This means that a span attribute MUST be used, as an Azure function app can host multiple functions that would usually share a TracerProvider.