With capabilities in Latest Dynatrace in place, migrate the remaining foundational configurations before starting the dashboards and alerting upgrades. This stage covers service naming rules, service detection, calculated metrics, processing rules, SLOs, and RVA monitoring rules, all of which are direct dependencies for upgrading dashboards and metric alerting.
Migrating your foundational configurations (service naming, metrics, SLOs, and processing rules) to Latest Dynatrace clears the dependency chain for dashboards and alerting: until calculated metrics and SLOs have Grail-backed equivalents, stage 7 and stage 8 cannot start.
Classic calculated metrics are precomputed with fixed dimensions and limited aggregation options. Latest Dynatrace metrics are backed by Grail, enabling advanced filtering, on-the-fly aggregation, and no metric explosion.
These configurations are dependencies for stage 7 and stage 8; complete all seven sub-steps before starting either stage.
Upgrade observability data and settings
| Role | Involvement | Responsibility |
|---|---|---|
| Dynatrace Admin | Required | Primary configuration owner for naming rules, metrics, SLOs, and security settings |
| Application Team Leads | Recommended | Validate that service names, metrics, and SLOs match expected values after migration |
| SRE / Observability Eng. | Recommended | Own calculated metric and SLO definitions that need conversion to DQL-based equivalents |
Inventory all active classic service naming rules and recreate equivalent naming logic in OpenPipeline.
Verify: Ratio of classic service naming rules vs. OpenPipeline equivalents at target coverage; service names match expected values across all monitored services.
Migrate service detection configuration to SDv2 classic runtime to ensure services are correctly detected under the Latest Dynatrace entity model.
Verify: All service detection rules migrated to SDv2; services detected correctly against expected baselines.
Inventory all classic calculated metrics and their consumers, then replace them with DQL-based equivalents that query Grail directly.
Verify: Ratio of classic calculated metrics vs. DQL-based equivalents at target coverage; metric values align between classic and Grail-backed queries.
Validate complex metric conversions carefully: metrics with complex entity selectors or multi-dimensional splits require careful DQL translation. Incorrect conversions produce silent data discrepancies that only surface during downstream dashboard or alert validation.
Inventory and recreate all active classic processing rules for logs and business events in OpenPipeline.
Verify: All active classic processing rules recreated in OpenPipeline; processing output validated against classic baselines.
Rebuild classic SLOs in Latest Dynatrace backed by Grail data and confirm metric parity against classic baselines.
Verify: Ratio of classic SLO definitions vs. Latest Dynatrace equivalents at target coverage; SLO burn rates and metric values match classic baselines within an acceptable variance.
Document acceptable variance before decommissioning: Latest Dynatrace SLOs backed by Grail may calculate slightly differently than classic SLOs during the parallel validation period. Document the variance and agree on an acceptable threshold before decommissioning classic SLOs.
Recreate classic runtime vulnerability analysis rules using the Latest Dynatrace security configuration and validate entity coverage.
Verify: Ratio of classic vs. Latest Dynatrace RVA monitoring rules at target coverage; entity coverage and vulnerability detection validated.
Once end users have validated the Latest Dynatrace SLOs, add the classic SLO app under the IAM boundary so users only see the latest experience.
Verify: Users in scope can access only the Latest Dynatrace SLO app; classic SLO app is no longer accessible to migrated user groups.
Stage complete when:
With configurations and settings migrated, you've established the foundation that dashboards and alerting both depend on. The next two stages (Upgrade dashboards and Upgrade metrics alerting and maintenance windows) share this prerequisite and can run in parallel. Coordinate across teams to assign ownership before starting both stages simultaneously.
The following resources support your work in this stage.
Reference for migrating service detection configuration to SDv2 classic runtime.
Upgrade from Metrics Classic to Metrics on Grail
Reference for migrating classic calculated metrics and metric selectors to DQL-based Grail equivalents.
Upgrade from classic pipeline to OpenPipeline
Guide for recreating classic processing rules as OpenPipeline processors.
Upgrade from Service-Level Objectives Classic to Service-Level Objectives
Step-by-step guide for rebuilding classic SLOs in Latest Dynatrace backed by Grail data.
Once configurations and settings are migrated, the next two stages can start simultaneously. Continue to stage 7: Upgrade dashboards and stage 8: Upgrade metrics alerting and maintenance windows in parallel.