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.
The following table describes how Dynatrace adds a specific messaging attribute alongside the original OpenTelemetry attribute.
| OpenTelemetry attribute | Added attribute |
|---|---|
|
|
|
|
|
|
For messaging.operation.type, the value send is normalized to publish.
Dynatrace automatically parses url.full and adds each component as a separate attribute. url.full itself is kept as is.
| Derived attribute | Description |
|---|---|
| The path component of the URL |
| The protocol scheme (for example, |
| The fragment identifier |
| The query string |
| The host address |
| The port number |
If your data contains deprecated OpenTelemetry HTTP attributes, Dynatrace keeps them and adds their current equivalents:
| Deprecated attribute | Current attribute |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
For http.target, Dynatrace splits the value into url.path and url.query.
If your data contains deprecated OpenTelemetry network attributes, Dynatrace keeps them and adds their current equivalents:
| Deprecated attribute | Current attribute |
|---|---|
|
|
|
|
|
|
|
|
If your data contains deprecated OpenTelemetry RPC message attributes, Dynatrace keeps them and adds their current equivalents:
| Deprecated attribute | Current attribute |
|---|---|
|
|
|
|
|
|
|
|
If your data contains deprecated OpenTelemetry database attributes, Dynatrace keeps them and adds their current equivalents:
| Deprecated attribute | Current attribute |
|---|---|
|
|
|
|
|
|
|
|
Dynatrace adds provider-specific attributes based on the standard OpenTelemetry cloud attributes, which stay unchanged.
Dynatrace adds provider-specific account attributes based on the standard cloud.account.id attribute:
| Cloud provider | OpenTelemetry attribute | Created attribute |
|---|---|---|
AWS |
|
|
Azure |
|
|
Google Cloud |
|
|
Dynatrace adds provider-specific region attributes based on standard cloud.region and related attributes:
| Cloud provider | OpenTelemetry attributes | Created attribute |
|---|---|---|
AWS |
|
|
Azure |
|
|
Google Cloud |
|
|
For Google Cloud, if multiple source attributes are present, they are evaluated in the order listed above.
When cloud.provider is azure, Dynatrace adds attributes extracted from cloud.resource_id:
| OpenTelemetry attribute | Created attribute |
|---|---|
|
|
|
|
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-000000000000azure.resource.group = MY-RESOURCE-GROUP