Dynatrace configuration
In addition to the application-side configuration, several Dynatrace-specific settings let you control how OpenTelemetry data is used in Dynatrace.
Enabling automatic OneAgent instrumentation
As described in Instrumentation, OneAgent supports the automatic instrumentation and ingestion of OpenTelemetry data for a number of technologies, which can be configured individually at Settings > Preferences > OneAgent features.
Attribute redaction
OpenTelemetry does not have an innate concept of data redaction. Data is collected and published to the backend as is.
For data safety purposes, and to prevent the accidental storage of personal or confidential data, the Dynatrace backend automatically filters supplied attributes and omits them in the web UI unless an attribute name is explicitly added to the allowlist. This enables you to meet your organization's privacy requirements and control the amount of monitoring data that is stored.
To configure attribute storage and masking settings for your environment
- In the Dynatrace menu, go to Settings.
- Select Server-side service monitoring > Attribute capturing.
- Add an attribute name to the allowlist.
- On the Attribute capturing page, select Allowed attributes.
- Dynatrace recommends a few basic attributes to generally be included, such as
service.name
orservice.version
. For ease of use, Dynatrace comes with a default configuration that can easily be adjusted.
- Dynatrace recommends a few basic attributes to generally be included, such as
- Select Add item to add a new key to the allowlist and enter the key.
- Select Save changes.
- On the Attribute capturing page, select Allowed attributes.
- Perform the following actions to mask a stored attribute value.
- On the Attribute capturing page, select Attribute data masking.
- Select Add item to add a new key to the masked attributed list.
- Enter a stored value key and select an option from the Masking dropdown list. To learn more about masking options, see OpenTelemetry traces.
- Select Save changes.
You can then find the attribute key on the Distributed traces page on the Summary tab.
Trace search limitations
Resource attributes
Searching by resource attribute is limited to the service name: filter by Service name
on the Distributed traces page.
Span attributes
Searching by span attribute is limited to the span name: filter by Request
on the Distributed traces page.