Navigating the New Platform
The first thing that changes after migration is the UI. Gen3 replaces the left sidebar with a unified app launcher. Instead of fixed menu items, every feature is an app — searchable, pinnable, and customizable.
🛠 Try it: Press Ctrl+K → type "Smartscape" → open it. You'll see your entire infrastructure as an interactive dependency graph: hosts → processes → services → applications. Click any node to drill into its health, then follow the connections to see what depends on it.
Key UI Changes
Notebooks Replace Data Explorer
The classic Data Explorer still exists but is a legacy feature tied to classic dashboards. Use Notebooks instead — interactive documents combining DQL queries, markdown notes, and shareable analysis.
🛠 Try it: Ctrl+K → "Notebooks" → Create new → Add a DQL section → type fetch dt.entity.host | limit 5
Dashboards Are DQL-Powered
Classic dashboards used pre-built tiles. Gen3 dashboards use DQL queries for every tile — more flexible, but requires DQL knowledge.
Problems View
The Problems screen looks similar but now shows data from dt.davis.problems in Grail. You can query problems with DQL directly.
Where Did My Settings Go?
GEN2 Location GEN3 Location
────────────────────────────────────── ──────────────────────────────────────
Settings → Monitoring → OneAgent Settings app → OneAgent
Settings → Anomaly detection Anomaly detectors app (or Settings)
Settings → Alerting → Alerting profiles Workflows app (no more alerting profiles)
Settings → Integration → Problem notif. Workflows app → email/Slack actions
Settings → Tags → Auto-tagging Settings app → Tags → Auto-tagging
Settings → Web and mobile → Apps RUM app → Application settings
Manage → Access tokens Access tokens still exist + OAuth clients
Manage → Deploy Dynatrace Deploy app (or Deployment API)
Account Management Portal
Gen3 introduces a separate Account Management portal for:
- User and group management (moved from environment level)
- OAuth client creation (for workflows, automation, and API access)
- Policy and permission management (ABAC)
- Environment provisioning and license management
💡 URL: myaccount.dynatrace.com (production) or your SSO portal. API tokens still work for many use cases — OAuth is required for workflows, dashboards, and account-level operations.
🔧 Migration Step: Restrict Users to Latest Apps
Once you're ready to migrate, you can restrict users to the latest Dynatrace apps so they stop using classic features:
- Go to Settings → General → Latest Dynatrace
- Enable "Restrict to latest apps" — this hides classic dashboards, classic alerting profiles, and other Gen2 UI elements
- Users will only see Gen3 apps (Dashboards, Notebooks, Workflows, Anomaly Detection)
⚠️ Only enable this AFTER you've migrated dashboards, alerts, and notifications. Otherwise users lose access to their tools before replacements are ready.
🔧 Migration Step: Export Your Gen2 Inventory
Before changing anything, export everything from your Gen2 environment:
# Option A: Export ALL configuration with Monaco (→ YAML)
monaco download \
--url https://YOUR-ENV.live.dynatrace.com \
--token-name DT_API_TOKEN \
--output-folder gen2-export
# Option B: Export with Terraform provider (→ .tf files)
# After terraform init, invoke the provider binary directly:
cd .terraform/providers/registry.terraform.io/dynatrace-oss/dynatrace/*/linux_amd64/
./terraform-provider-dynatrace -export -ref
# Both create files for every setting, dashboard, alert, MZ, etc.
# Use this as your migration reference and rollback safety net
💡 The Monaco or Terraform export is your insurance policy. Even if you use the built-in upgrade tools, having a full export means you can always recreate anything that goes wrong. Monaco exports YAML, Terraform manages state — use whichever fits your workflow.