
Dt Migration
If you're migrating Dynatrace queries from classic or Gen2 entity syntax to Smartscape, this walks you through it systematically. It breaks migrations into three scenarios: mass data queries filtered by entity conditions, mass data queries using entity subqueries, and pure entity list queries. Each gets a different strategy. The skill includes lookup tables for mapping old entity types like dt.entity.host to new Smartscape equivalents, covers relationship traversal patterns, and flags constructs like entityName and classicEntitySelector that need explicit rewrites. It's thorough but assumes you already know DQL. Load dt-dql-essentials alongside it if you want the final query to follow current syntax rules too.
- skills.sh installs
- 2.6K
- GitHub stars
- 177
- last updated
- Aug 21, 2026
Install
$ npx -y skills add dynatrace/dynatrace-for-ai --skill dt-migration --agent claude-codeInstalls into .claude/skills of the current project.
Files
Smartscape Migration Skill
This skill migrates Dynatrace classic and Gen2 entity-based DQL queries and query patterns to Smartscape-based equivalents.
Load the dt-dql-essentials skill before writing final DQL so the translated query also follows current DQL syntax rules.
This skill focuses on Smartscape-oriented DQL migration only. It does not cover asset-level migration workflows.
Query Purpose Classification
Start here. The correct migration strategy depends on what the query is actually trying to do — not just which classic constructs it uses.
There are three distinct situations:
Sponsors
Details
- Repository
- github.com/dynatrace/dynatrace-for-ai
- First seen
- Jun 3, 2026