Latest Dynatrace
Distributed traces are stored in the default_span
built-in Grail bucket with a 10-day retention period. Traces might contain personal and sensitive data.
This article contains information on how to modify user access to trace data and sensitive information and how to configure trace data storage.
This article is intended for administrators controlling identity and access management.
To configure user permission to fetch span data from buckets and tables in Grail and for Distributed Tracing data
ALLOW storage:buckets:read WHERE storage:bucket-name = "spans";ALLOW storage:spans:read;
Users can now access all stored trace data and leverage it in Grail according to sensitive information permissions. To change which data users can access, you can modify environment-level data storage and user access to sensitive information.
To configure access to sensitive information in compliance with your company's privacy policies
ALLOW storage:fieldsets:read WHERE storage:fieldset-name="builtin-sensitive-spans"
The fields' attributes are client.ip
, db.connection_string
, http.request.header.referer
, url.full
, url.query
, and db.query.parameters
. To learn more about the attributes, see Global field reference.
ALLOW storage:fieldsets:read WHERE storage:fieldset-name="builtin-request-attributes-spans"
Users can now access sensitive data according to the configured permissions.
To configure which span data is stored and available in your latest Dynatrace environment
Only attributes that are not blocked will be forwarded to Grail.