Try it free

Extending OTel data with Dynatrace Semantic Dictionary conventions

  • Latest Dynatrace
  • Reference
  • 2-min read

Dynatrace preserves the original attributes of your OpenTelemetry data. At ingest, Dynatrace enriches your data by adding attributes alongside the originals, for example, current names for deprecated attributes, URL components parsed from url.full, and provider-specific cloud attributes. These added attributes let Dynatrace apps, analytics, and visualizations work with your OpenTelemetry data without changes to your instrumentation.

The Dynatrace Semantic Dictionary is largely aligned with the OpenTelemetry semantic conventions, so you can instrument with standard OpenTelemetry attributes—no Dynatrace-specific attributes are required.

This page describes how Dynatrace handles spans/traces.

Similar functionality is also being developed for metrics and logs, but isn't currently generally available. For more information, see Extending OTel data with Dynatrace Semantic Dictionary conventions.

Messaging operations

The following table describes how Dynatrace adds a specific messaging attribute alongside the original OpenTelemetry attribute.

OpenTelemetry attributeAdded attribute

messaging.operation

messaging.operation.type

For messaging.operation.type, the value send is normalized to publish.

URL parsing

Dynatrace automatically parses url.full and adds each component as a separate attribute. url.full itself is kept as is.

Derived attributeDescription

url.path

The path component of the URL

url.scheme

The protocol scheme (for example, https)

url.fragment

The fragment identifier

url.query

The query string

server.address

The host address

server.port

The port number

If your data contains deprecated OpenTelemetry HTTP attributes, Dynatrace keeps them and adds their current equivalents:

Deprecated attributeCurrent attribute

http.url

url.full

http.method

http.request.method

http.status_code

http.response.status_code

Cloud provider attributes

Dynatrace adds provider-specific attributes based on the standard OpenTelemetry cloud attributes, which stay unchanged.

Account and project identifiers

Dynatrace adds provider-specific account attributes based on the standard cloud.account.id attribute:

Cloud providerOpenTelemetry attributeCreated attribute

AWS

cloud.account.id

aws.account.id

Azure

cloud.account.id

azure.subscription

Google Cloud

cloud.account.id

gcp.project.id

Regional attributes

Dynatrace adds provider-specific region attributes based on standard cloud.region and related attributes:

Cloud providerOpenTelemetry attributesCreated attribute

AWS

cloud.region

aws.region

Azure

cloud.region

azure.location

Google Cloud

gcp.location
gcp.zone
cloud.region
cloud.availability_zone

gcp.region

For Google Cloud, if multiple source attributes are present, they are evaluated in the order listed above.

Related tags
Application Observability