Best practices for upgrading to the latest Dynatrace

Latest Dynatrace
Overview
1-min read

Upgrading to the latest Dynatrace moves your environment to a platform backed by Grail and built for enterprise scale. The upgrade is a phased process: you get oriented with new concepts, reconfigure governance and access, then migrate each area of your observability stack in turn.

Get oriented

The latest Dynatrace replaces management zones and classic configurations with new concepts for data storage, access, and segmentation. Start here before making changes to your environment.

Things to know before upgrading to the latest Dynatrace

Explanation

Read this explanation

Differences between classic auto-tagging and primary Grail tags

Understand how the Dynatrace Classic auto-tagging and management zones compare to primary Grail fields and tags, and why Latest Dynatrace is simpler to maintain.

Explanation

Read this explanation

Best practice examples - from Management Zones to Segments

Investigate different scenarios with concrete examples of how to upgrade your management zones to segments.

Best practices

Explore these best practices

Dynatrace Platform Foundations

Set up data access and governance

Working with policies: Configure permission policies to control access to Dynatrace data
Configure advanced permissions with security context: Restrict data visibility with fine-grained, attribute-based access control
Set up Grail permissions for:
- Logs: Control who can query and manage log data in Grail
- Metrics: Control who can query and manage metric data in Grail
- Distributed tracing: Control who can query and manage traces in Grail
- OneAgent: Control who can access OneAgent data in Grail
- OpenTelemetry: Control who can access OpenTelemetry data in Grail
- Kubernetes: Control who can access Kubernetes telemetry in Grail

Platform fundamentals

APIs: Upgrade from deprecated APIs to current API endpoints

Cost allocation

General: Configure cost centers and allocation models for your environment
Kubernetes deployments: Allocate costs from Kubernetes deployments to cost centers and products
OneAgent deployments: Allocate costs from OneAgent deployments to cost centers and products

Keep problems and alerting working

Problems: Upgrade from Problems Classic to the Problems app
Metric alerting: Upgrade from classic metric alerting to the Anomaly Detection app
Alert notifications: Upgrade from classic alert notifications to alerting and notifications
Service-Level Objectives: Upgrade from Service-Level Objectives Classic to Service-Level Objectives

Migrate your data pipeline

Processing rules: Upgrade from classic processing rules to OpenPipeline

Preserve metrics and service visibility

Metrics: Upgrade from classic metrics to Grail-powered metrics
Metric selectors: Convert your classic metric selectors to DQL equivalents in Grail metrics
Runtime metrics: Upgrade runtime metrics from Classic to Grail metrics
Kubernetes metrics: Upgrade Kubernetes metrics from Classic to Grail metrics
Service metrics: Upgrade service metrics from Classic to Grail metrics
Calculated service metrics: Upgrade calculated service metrics from Classic to Grail metrics
RUM metrics: See how RUM Classic metrics map to their Grail metrics equivalents

Get your apps and monitoring surfaces working

Dashboards: Upgrade from Dashboards Classic to Dashboards
RUM: Upgrade from Real User Monitoring Classic to Real User Monitoring
Vulnerabilities: Upgrade from classic vulnerabilities apps to the Vulnerabilities app

Upgrade infrastructure observability and security

Log monitoring: Upgrade from Log Monitoring Classic to Log Analytics
- Conversion to DQL for logs: Convert your classic log monitoring rules to DQL in Log Analytics
AWS services: Upgrade from classic AWS services to current AWS cloud services
Kubernetes: Upgrade from Classic to Kubernetes app monitoring