Try it free

Extending OTel data with Dynatrace Semantic Dictionary conventions

  • Latest Dynatrace
  • Reference
  • 3-min read
  • Published Oct 23, 2026
  • Preview
Preview

Extended OpenTelemetry semantic mapping is currently in preview and available only for a limited number of selected environments—users in the selected environments will be notified by email.

Information about general availability will be provided in a future release notes entry.

Dynatrace preserves the original attributes of your OpenTelemetry data. At ingest, Dynatrace enriches your data by adding attributes alongside the originals. This applies to ingested spans, metrics, and logs.

The Dynatrace Semantic Dictionary is largely aligned with the OpenTelemetry semantic conventions.

  • You can instrument with standard OpenTelemetry attributes.
  • No Dynatrace-specific attributes are required.
  • You don't need to manually configure OpenPipeline processors.

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

messaging.kafka.consumer.group

messaging.consumer.group.name

messaging.client_id

messaging.client.id

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

http.target

url.path, url.query

http.flavor

network.protocol.version

http.user_agent

user_agent.original

For http.target, Dynatrace splits the value into url.path and url.query.

Network attributes

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

Deprecated attributeCurrent attribute

net.peer.ip

network.peer.address

net.host.ip

network.local.address

net.host.name

server.address

net.host.port

server.port

RPC attributes

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

Deprecated attributeCurrent attribute

message.type

rpc.message.type

message.id

rpc.message.id

message.compressed_size

rpc.message.compressed_size

message.uncompressed_size

rpc.message.uncompressed_size

Database attributes

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

Deprecated attributeCurrent attribute

db.statement

db.query.text

db.system

db.system.name

db.name

db.namespace

db.operation

db.operation.name

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.

Azure resource ID attributes

When cloud.provider is azure, Dynatrace adds attributes extracted from cloud.resource_id:

OpenTelemetry attributeCreated attribute

cloud.resource_id

azure.subscription

cloud.resource_id

azure.resource.group

For example, from /SUBSCRIPTIONS/00000000-0000-0000-0000-000000000000/RESOURCEGROUPS/MY-RESOURCE-GROUP/PROVIDERS/MICROSOFT.WEB/SITES/MY-APP, Dynatrace extracts:

  • azure.subscription = 00000000-0000-0000-0000-000000000000
  • azure.resource.group = MY-RESOURCE-GROUP
Related tags
Application Observability