Try it free

Enrich ingested signals

  • Latest Dynatrace
  • Upgrade guide

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.

Why enrich?

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.

  • All signals carry the required metadata: logs, traces, metrics, and events enriched with primary Grail fields and tags give the platform the context it needs to configure team access, partition data by cost center or product, and surface the right signals to the right people
  • Foundation for access control and cost allocation: with enrichment in place, IAM, segments, and bucket routing can all be configured correctly the first time

What will you do?

This stage is iterative. Validate coverage, fix gaps, then re-validate, repeating the cycle until enrichment meets the agreed threshold.

  1. Validate that observability components meet minimum version requirements for enrichment
  2. Measure enrichment coverage across all signal types using the Enrichment Coverage Dashboard
  3. Close enrichment gaps using ingest enrichment, OpenPipeline, and other post-ingest mechanisms

Before you begin

At a glance

  • Estimated effort: 1–4 days
  • Estimated timeline: 1–3 weeks

Prerequisites

Upgrade scoping: scope document signed off and classic configuration inventory complete.

Key stakeholders

RoleInvolvementResponsibility
Dynatrace AdminRequiredConfigures enrichment rules, OpenPipeline processors, and ingest enrichment
Data OwnerRecommendedOwns the source-of-truth for dimension mappings
Application TeamsRecommendedConfirm their data is enriched correctly and flag gaps
FinOps / SecurityOptionalUse enriched dimensions for cost allocation and access control validation

Enrich ingested signals

1. Validate observability component compatibility

Confirm that all observability components meet the minimum version requirements to support primary Grail fields and tags enrichment.

  1. Review the minimum version requirements for enrichment support (for example, OneAgent version 1.343+). For details, see Configure ingest enrichment rules.
  2. Identify components below the minimum version threshold.
  3. Coordinate upgrades for out-of-date components before proceeding to the next step.

Verify: All observability components at or above the minimum required version for supporting enrichment capabilities.

2. Validate enrichment coverage

Use the Enrichment Coverage Dashboard to measure signal coverage and pinpoint which signals or resources are missing required metadata.

  1. Get the Enrichment Coverage Dashboard: open the Enrichment Coverage Dashboard in the Dynatrace Playground, download it, and then upload it to your environment.
  2. Use the dashboard to measure coverage for dt.security_context, dt.cost.costcenter, dt.cost.product, and primary_tags.* across all signal types.
  3. Identify which signals or resources are missing the required metadata, for example, host X doesn't have the dt.security_context defined.
  4. Document gaps by signal type, technology, and responsible team.

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.

3. Close enrichment gaps

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.

  1. For each gap, select the appropriate enrichment mechanism, following Best practices for enriching primary Grail fields and tags.
  2. Implement metadata enrichment configurations for the selected mechanisms.
  3. Check the Enrichment Coverage Dashboard again to confirm coverage improved.
  4. Repeat the validate-fix cycle until the enrichment ratio meets the agreed success 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:

  • All observability components are at or above the minimum required version for primary_tags.* enrichment
  • Enrichment coverage for dt.security_context, dt.cost.costcenter, dt.cost.product, and primary_tags.* is at or above the agreed threshold across all signal types

With 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.

Documentation and best practices

The following resources support your work in this stage.

  • Primary Grail fields and tags

    How primary Grail fields and tags form the metadata foundation of Dynatrace, enabling routing, access control, cost allocation, and segmentation across all signal types.

  • Plan your tagging strategy

    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.

  • Configure security context

    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.

Ready for more?

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.

Related tags
Dynatrace Platform