If you're running Dynatrace Classic auto-tagging and management zones, use these guides to move to primary Grail fields and tags.
Before you pick a guide below, decide what you need, not where it comes from. The same decision applies whether your tags originate from OneAgent, Kubernetes, or a cloud provider.
team, appid, environment, business_unit, or cmdbid. These are meaningful on every signal.last_restarted, deployment-tool, helm-version, or last-audited-by. These describe an entity, not a signal, and don't belong as primary tags.Then pick the guide below for where your telemetry originates to see the exact configuration steps.
Upgrade from OneAgent classic auto-tagging to primary Grail tags and fields.
Upgrade Kubernetes telemetry enrichment rules to the central primary Grail tag configuration.
Upgrade from classic AWS, Azure, and GCP tag propagation to primary Grail tags.
Upgrade classic OpenTelemetry resource-attribute tagging to primary Grail tags.