Enriching primary Grail fields and tags correctly makes it easier to filter, route, and govern your observability data. The approaches on this page are ordered from zero-configuration defaults to ingest-time derivation. Start at the top and move to the next only if the previous approach doesn't meet your needs. Each approach adds configuration effort, so apply only as much as your use case requires. For domain-specific guidance, see OneAgent and Kubernetes.
Check built-in Dynatrace coverage
Enrich at deployment
Configure centrally
Use OpenPipeline for ingest-time enrichment
Many primary Grail fields are automatically populated: the Kubernetes cluster and namespace, host group, and cloud account require no configuration. If these cover your filtering and access needs, no further setup is required.
Set tags at deployment time so every signal is enriched from the start, before it reaches the pipeline.
Promote existing cloud tags, Kubernetes labels, or host properties to primary Grail tags through central configuration, without modifying individual deployments.
Derive or assign primary Grail tags from existing signal fields at ingest-processing time using OpenPipeline primary Grail tag rules. Use it only
primary_tags.* when provider field names differ across record types—for example, to map cloud and Kubernetes tag fields or when each cloud provider uses a different field name for the same tag.