This documentation describes the new tagging model for latest Dynatrace. Some capabilities are still rolling out. If you're currently using classic auto-tagging, see Classic vs. latest to understand how your existing setup maps to the new model.
Tags add the organizational context that turns telemetry into something teams can act on. In Dynatrace, a consistent tagging strategy lets you carry ownership, environment, application, and cost information across logs, metrics, spans, events, and Smartscape nodes, so the same metadata is available in both telemetry and topology.
Teams use tags in Dynatrace to solve a small set of high-value problems repeatedly across environments and signal types.
Learn what tags are and why they matter.
Learn how primary Grail fields and tags form the metadata foundation of the Dynatrace platform.
Follow a fallback approach to enriching your signals, from out-of-the-box defaults to ingest-time lookup.
Compare classic auto-tagging with primary Grail fields and tags.
Use your classic setup as input for primary Grail fields and tags.
Coming soon
Apply primary Grail fields and tags through OneAgent installation and runtime configuration.
Promote Kubernetes labels and annotations to primary Grail fields and tags using the Dynatrace Operator.
Enrich data from Dynatrace extensions with primary Grail fields and tags.
Coming soon
Propagate AWS resource tags to primary Grail fields and tags for unified observability.
Coming soon
Propagate Azure resource tags to primary Grail fields and tags for unified observability.
Coming soon
Propagate Google Cloud labels to primary Grail fields and tags for unified observability.
Coming soon
Apply tags in Real User Monitoring and Synthetic Monitoring for digital experience observability.
Coming soon
Set primary Grail tags programmatically using the Dynatrace API.
Coming soon
Map OpenTelemetry resource attributes to primary Grail fields and tags.
Coming soon