Upgrade observability data and settings

Latest Dynatrace
Upgrade guide
Published Jul 24, 2026

Upgrade capabilities to Latest Dynatrace: RUM, cloud integrations, extensions, and classic log ingestion. Route logs through OpenPipeline and Grail. Once end users validate and approve the Latest Dynatrace experience, promote it as the default.

Why upgrade?

Upgrading your observability capabilities to Latest Dynatrace consolidates metrics, logs, and traces into a single query-based experience backed by Grail, replacing siloed classic monitoring with a unified platform.

Query-based access to all observability data: metrics, logs, and traces queryable with greater flexibility and interactivity than classic, enabling precise analysis and investigation across all sources

What will you do?

This stage upgrades each observability capability area independently. The sub-steps can be distributed across teams, but the promote step comes last, only after all teams have validated their Latest Dynatrace experience.

Upgrade RUM applications to Latest Dynatrace
Upgrade cloud platform monitoring to Latest Dynatrace cloud connections
Upgrade extensions to Extension Framework 2.0
Upgrade classic log ingestion through OpenPipeline and Grail
Promote Latest Dynatrace RUM and cloud as the primary experience

Before you begin

At a glance

Estimated effort: 2–10 days
Estimated timeline: 1–3 weeks

Prerequisites

Upgrade management zones to IAM & segments

Key stakeholders

Role	Involvement	Responsibility
Dynatrace Admin	Required	Primary configuration owner for all capability areas in this stage
DevOps / Platform Eng.	Recommended	Owns cloud integrations, log pipelines, and extension configurations
Cloud Ops	Recommended	Needed for cloud connection upgrades and resource discovery validation
Security Team	Optional	Validates monitoring coverage after migration

Upgrade your observability data and settings

1. Upgrade RUM to Latest Dynatrace

Migrate classic Real User Monitoring applications to the Latest Dynatrace RUM framework and validate user action tracking and session replay.

For each classic RUM application, create a corresponding Latest Dynatrace RUM application.
Update the JavaScript tag or mobile SDK to the latest version for each application.
Configure user action naming, conversion goals, and key user actions to match classic settings.
Enable session replay on the latest application and confirm replay captures match classic behavior.
Validate that RUM data flows into Grail and is queryable via DQL.

Verify: Ratio of classic vs. Latest Dynatrace RUM applications at target coverage; session replay and user action tracking confirmed against classic baselines.

2. Upgrade cloud platform monitoring

Replace classic cloud integrations with Latest Dynatrace cloud connections and verify resource discovery, metadata enrichment, and monitoring coverage.

For each cloud account, create a new Latest Dynatrace cloud connection with equivalent scope.
Configure role-based or credential-based access for the new connection.
Confirm that cloud resources are discovered and enriched with the expected metadata.
Disable classic cloud connections once latest connections cover the same resource scope.

Verify: Ratio of classic vs. Latest Dynatrace cloud connections at target coverage; cloud resource discovery and metadata enrichment validated across all target accounts.

Rotate credentials before switching connections: switching from classic to Latest Dynatrace cloud connections requires new credentials or role assignments. In some scenarios, DAC cannot run in parallel with classic integration and a switchover is needed. Coordinate with Cloud Ops early to avoid delays.

3. Upgrade extensions

Ensure active extensions are running on Extension Framework 2.0 with proper Latest Dynatrace enrichment.

List all active classic extensions and verify whether an Extension Framework 2.0 equivalent exists for each.
Migrate each extension with a 2.0 equivalent; document those without one as a monitoring gap requiring an alternative solution or accepted risk.
Validate that extension monitoring data matches classic extension output for key metrics.
Confirm that 2.0 extensions produce signals enriched with the expected primary_tags.* and other enrichment attributes.

Verify: Ratio of extensions on Extension Framework 2.0 with proper enrichment at target coverage; monitoring gaps documented for any extensions without 2.0 equivalents.

Document extensions without 2.0 equivalents: not all classic extensions have 2.0 equivalents. Missing extensions leave monitoring gaps that need alternative solutions or accepted risk documentation before closing this step.

4. Upgrade Log Monitoring Classic to Grail

Route log ingestion through OpenPipeline, configure processing rules, and confirm logs are queryable in Grail.

Configure log ingestion sources to route through OpenPipeline instead of classic log ingest.
Recreate classic log processing rules (parsing, masking, routing) as OpenPipeline processors.
Confirm that logs are ingested and queryable in Grail via DQL.

Verify: Log ingestion ratio (classic vs. OpenPipeline/Grail) at target coverage; logs confirmed queryable in Grail with correct processing applied.

5. Promote Latest Dynatrace RUM and cloud as the primary experience

Once end users have validated and approved the Latest Dynatrace experience, update the IAM Segment boundary to surface it as the default so users naturally land on the latest view.

Confirm that all affected teams have reviewed and approved their Latest Dynatrace RUM applications and cloud monitoring views.
Update the IAM Segment boundary to surface Latest Dynatrace RUM and cloud as the primary experience.
Communicate the change to affected users so they know where to navigate.
Monitor for any reports of missing data or unexpected behavior after the boundary update.

Verify: IAM Segment boundary updated; users consistently landing on Latest Dynatrace RUM and cloud views with no escalations from affected teams.

Stage complete when:

All RUM applications, cloud connections, and extensions are at target coverage in Latest Dynatrace
Log ingestion is routed through OpenPipeline and Grail at target coverage
IAM Segment boundary is updated and users are consistently landing on Latest Dynatrace views with no escalations

With your observability capabilities upgraded and data flowing into Grail, you're ready to optimize how that data is stored. The next stage is Partition your Grail data: assess signal volumes and configure bucket routing to keep query performance predictable and retention policies aligned with your compliance requirements.

Documentation and best practices

The following resources support your work in this stage. Documentation covers platform concepts, configuration reference, and related guides; best practice cards provide implementation guidance from Dynatrace experts.

Upgrade from RUM Classic to RUM

Migrate classic Real User Monitoring applications to the latest RUM framework.
Upgrade Log Monitoring Classic to Log Management and Analytics

Guide for routing classic log ingestion through OpenPipeline and Grail.
Best practices for upgrading classic cloud monitoring

Plan and execute a full migration from classic cloud monitoring to the Latest Dynatrace Cloud Platform Monitoring architecture.

For additional community guidance, see Transition from Classic to new Application Security monitoring and Latest Services app vs. Classic on the Dynatrace Community.

Ready for more?

When all observability capabilities are live in Latest Dynatrace and users are on the promoted experience, assess signal volumes and configure bucket routing. For environments that don't require custom bucket routing, this stage can be light; the goal is to validate that default routing meets your query performance and retention needs before starting configuration migration.

Continue to Partition your Grail data.