dt-migration

Name: dt-migration
Availability: InStock
Author: Dynatrace

Migrate classic and Gen2 DQL queries to Smartscape DQL.

120|26|Updated Mar 31, 2026

Search Tags:#migration #topology #mapping #dql #query-translation #dynatrace #smartscape

Ready to run

npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-migration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dt-migration
Source: https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-migration
Command: npx skills add https://github.com/Dynatrace/dynatrace-for-ai --skill dt-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transforms legacy Dynatrace DQL written for classic and Gen2 entity models into Smartscape-based DQL, enabling agents to query the modern Smartscape topology with fewer manual rewrites.

Core Features & Use Cases

Rewrites classic DQL patterns, such as entityName(), entityAttr(), and classicEntitySelector(), into Smartscape idioms like getNodeName(), getNodeField(), and traverse.
Helps migrate topology navigation across hosts, services, Kubernetes workloads, containers, and cloud applications using accurate edge mappings and smartscapeNodes/ smartscapeEdges.
Provides a guided workflow with links to type mappings, relationship mappings, and example migrations to reduce error-prone ad-hoc rewrites.

Quick Start

Translate a sample classic DQL query into a Smartscape query using the reference guides.

Frequently Asked Questions about dt-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate classic Dynatrace DQL queries to Smartscape?▼

To migrate Dynatrace DQL to Smartscape, translate entity patterns and topology queries using mapping references. Replace functions like entityName() and classicEntitySelector() with Smartscape idioms like getNodeName() and traverse to produce validated queries.

How does topology navigation work when migrating to Smartscape DQL?▼

Smartscape topology navigation uses edge mappings with smartscapeNodes and smartscapeEdges to traverse relationships. This replaces classic entity model traversals across hosts, services, Kubernetes workloads, containers, and cloud applications with accurate edge mappings.

Can I use this to translate entityAttr() functions for Kubernetes workloads?▼

Yes, you can translate entityAttr() functions for Kubernetes workloads by replacing them with getNodeField() operations. The migration references provide specific type mappings and relationship mappings for Kubernetes and container topology queries.

What is the best way to rewrite classicEntitySelector patterns in Gen2 DQL?▼

The best way to rewrite classicEntitySelector patterns is to use the provided migration workflow and deep guides to convert them into Smartscape traverse operations. This ensures accurate topology validation and surfaces explicit migration notes for your queries.

What are the limitations of manually converting DQL to Smartscape without references?▼

Manual DQL conversion without references leads to error-prone ad-hoc rewrites and incorrect topology queries. Using guided type mappings, relationship mappings, and example migrations prevents these errors when translating legacy entity model queries.

Do I need to validate topology after translating Dynatrace queries?▼

Yes, you need to validate topology after translating Dynatrace queries to ensure the Smartscape DQL output is correct. The migration workflow includes validation steps and surfaces explicit migration notes to verify edge mappings and relationship accuracy.