dt-migration

Translate Dynatrace classic and Gen2 DQL queries into Smartscape DQL.

2|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-migration-israel-salgado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-migration
Source: https://github.com/israel-salgado/dt-mcp-server/tree/main/.agents/skills/dt-migration
Command: npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-migration-israel-salgado

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrate Dynatrace classic and Gen2 DQL patterns to Smartscape equivalents, enabling teams to translate legacy queries and mappings into modern topology-based queries.

Core Features & Use Cases

  • Convert classic and Gen2 DQL patterns to Smartscape constructs like smartscapeNodes, smartscapeEdges, and traverse.
  • Provide guidance for entity migrations such as host, service, Kubernetes, and container-related patterns.
  • Include end-to-end workflow references and mapping tables to ensure consistent results across environments.

Quick Start

Translate a sample query to Smartscape DQL and review the mapping rationale.

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 DQL queries to Smartscape?

You can migrate Dynatrace DQL queries to Smartscape by translating classic and Gen2 fetch patterns, classicEntitySelector, and dt.entity.* signal dimensions into smartscapeNodes and traversal-based queries using official mapping references.

What is the best way to convert classicEntitySelector patterns to Smartscape topology queries?

Converting classicEntitySelector patterns involves mapping legacy entity selections to smartscapeNodes and smartscapeEdges constructs, utilizing traversal-based queries to represent appropriate topology edges and relationships.

How does the Dynatrace Gen2 DQL to Smartscape translation handle entity mappings?

The translation handles entity mappings by covering host, service, Kubernetes, and container-related patterns, converting dt.entity.* signal dimensions into modern topology-based queries with consistent results across environments.

Does the Smartscape DQL migration support Kubernetes and container entities?

Yes, the migration supports Kubernetes and container-related patterns by providing specific entity migration guidance and mapping tables to translate legacy Dynatrace queries into Smartscape equivalents.

What happens when there is no exact Smartscape equivalent for a Dynatrace DQL pattern?

When an exact equivalent is unclear, the migration process enforces core rules and surfaces explicit assumptions, ensuring you understand the translation rationale and any limitations in the converted Smartscape query.