dt-migration

Translate classic and Gen2 Dynatrace DQL queries into Smartscape-based equivalents.

Updated Aug 23, 2026

Search Tags:#automation #workflow #migration #migrate #dql #dynatrace #smartscape

Ready to run

npx skills add https://github.com/virtualrussel/dynatrace-ai-workspace --skill dt-migration-virtualrussel

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Dynatrace environments often rely on legacy DQL patterns and nested entity patterns. This skill provides automated migration from classic and Gen2 queries to Smartscape-based equivalents, enabling modern, scalable querying without manual rewrites.

Core Features & Use Cases

Migrate old DQL patterns to Smartscape queries, including rewriting entityName, entityAttr, and classicEntitySelector patterns.
Translate classic topology and relationship navigation to Smartscape primitives: traverse, references, and smartscapeEdges.
Load and apply detailed reference guides (type mappings, migration workflow) to ensure correct, production-ready translations.

Quick Start

Translate a given classic or Gen2 Dynatrace DQL query into a Smartscape-based equivalent and present the migrated query.

Frequently Asked Questions about dt-migration

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

FAQPage Schema

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

Dynatrace DQL migration converts classic and Gen2 queries into Smartscape equivalents by rewriting entityName, entityAttr, and classicEntitySelector patterns into traverse, references, and smartscapeEdges primitives for modern topology navigation.

What does converting dt.entity.* patterns to Smartscape involve?▼

Converting dt.entity.* patterns involves mapping classic relationships to Smartscape primitives like traverse, references, and smartscapeEdges, loading detailed type mappings and migration workflow references to ensure production-ready translated queries.

Can I automate rewriting entityName and entityAttr calls in Dynatrace?▼

Yes, automating the rewrite of entityName and entityAttr calls translates them into Smartscape-based equivalents, applying detailed reference guides to ensure correct mapping without manual query rewrites across your Dynatrace environment.

When do I need to translate classicEntitySelector patterns to Smartscape?▼

You need to translate classicEntitySelector patterns when migrating legacy nested entity patterns to Smartscape to enable modern, scalable querying of Dynatrace data without maintaining outdated classic topology navigation logic.

What happens if exact DQL to Smartscape mappings are unclear?▼

When exact mappings are unclear, the migration surfaces explicit assumptions during translation by loading core mappings and migration workflow references first, ensuring transparency before writing the final Smartscape query equivalents.

Does this migration approach handle both classic and Gen2 Dynatrace queries?▼

Yes, this migration approach handles both classic and Gen2 Dynatrace DQL queries, translating them into Smartscape-based equivalents to enable modern querying while applying detailed type mappings for production-ready translations.