Identify signals without proper enrichment and close gaps using ingest enrichment, OpenPipeline, and other post-ingest mechanisms. This stage runs after data ingestion has started and is iterative: validate coverage, fix gaps, re-validate until the enrichment ratio meets your defined threshold.
Metadata enrichment is the most critical preparation step in the entire upgrade: every downstream stage depends on primary Grail fields and tags being consistently applied before IAM, segments, or cost allocation can be configured correctly. Gaps in enrichment propagate into misconfigured access control, broken segmentation, and inaccurate cost attribution.
This stage is iterative. Validate coverage, fix gaps, then re-validate, repeating the cycle until enrichment meets the agreed threshold.
Upgrade scoping: scope document signed off and classic configuration inventory complete.
| Role | Involvement | Responsibility |
|---|---|---|
| Dynatrace Admin | Required | Configures enrichment rules, OpenPipeline processors, and ingest enrichment |
| Data Owner | Recommended | Owns the source-of-truth for dimension mappings |
| Application Teams | Recommended | Confirm their data is enriched correctly and flag gaps |
| FinOps / Security | Optional | Use enriched dimensions for cost allocation and access control validation |
Confirm that all observability components meet the minimum version requirements to support primary Grail fields and tags enrichment.
Verify: All observability components at or above the minimum required version for supporting enrichment capabilities.
Use the Enrichment Coverage Dashboard to measure signal coverage and pinpoint which signals or resources are missing required metadata.
dt.security_context, dt.cost.costcenter, dt.cost.product, and primary_tags.* across all signal types.dt.security_context defined.Verify: Enrichment coverage report generated with all gap areas identified before starting remediation.
Validate enrichment coverage first: insufficient enrichment at this step results in poorly configured access control, segmentation, and cost allocation across all downstream upgrade stages. Do not skip or abbreviate the coverage validation.
Apply ingest enrichment, OpenPipeline processors, and other post-ingest mechanisms to close the gaps identified in the previous step. Repeat the validate → close → re-validate cycle until coverage meets the agreed threshold.
Verify: Enrichment coverage for dt.security_context, dt.cost.costcenter, dt.cost.product, and primary_tags.* at or above the agreed threshold across all signal types.
Refresh your lookup tables regularly: enrichment maps not refreshed after team or product changes attribute data to retired owners. Agree on a refresh cadence with the data owner before closing this stage.
Account for backfill limitations: enrichment applies only to signals ingested after the rule is active. Historical queries may show inconsistent dimensions for signals ingested before enrichment was in place.
Stage complete when:
primary_tags.* enrichmentdt.security_context, dt.cost.costcenter, dt.cost.product, and primary_tags.* is at or above the agreed threshold across all signal typesWith enrichment validated across all signal types, you have the metadata foundation that every downstream stage depends on. The next stage is Upgrade management zones to IAM and segments: configure access boundaries and dynamic segment-based filters using the enrichment attributes you've now applied consistently.
The following resources support your work in this stage.
How primary Grail fields and tags form the metadata foundation of Dynatrace, enabling routing, access control, cost allocation, and segmentation across all signal types.
How to build a tagging strategy in Dynatrace using primary Grail fields and tags to organize, govern, and secure your observability data.
Best practices for enriching primary Grail fields and tags
A step-by-step fallback approach for enriching primary Grail fields and tags, from built-in defaults to ingest-time enrichment with OpenPipeline.
Set dt.security_context to enable record-level access control on telemetry data for shared infrastructure, regulated environments, and multi-tenant setups.
Organize your data with primary Grail fields and tags
Overview of Dynatrace tagging, including ingest enrichment and tag strategies for enrichment at scale.
Apply primary Grail tags across an example AWS estate
Apply a single primary Grail tag schema across Kubernetes, EC2, Lambda, RDS, RUM, and Synthetic using ingest enrichment rules and OpenPipeline.
When enrichment coverage meets the agreed threshold, you're ready to configure the access boundaries that IAM, segments, and filtering all depend on. The enrichment metadata you've applied here will directly drive segment definitions and IAM policy scope in stage 3.
Continue to stage 3: Upgrade management zones to IAM and segments.