dynatrace/dynatrace-for-ai

dt-migration

Migrate Dynatrace classic and Gen2 entity-based DQL to Smartscape equivalents.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/dynatrace/dynatrace-for-ai --skill dt-migration

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

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:

#SituationClassic anti-patternMigration strategy
1Mass data query filtered by entity conditionsclassicEntitySelector(...) inline in filter: of a timeseries, logs, or metrics queryResolve entity conditions to raw data dimensions first. Smartscape is a fallback, not the default.
2Mass data query using entity subquery for filteringfetch dt.entity.* inside in [...], lookup [...], or join [...] to filter the outer mass data querySame dimension-first strategy. Rewrite as raw dimension filter or in [smartscapeNodes ...] subquery.
3Pure entity list queryfetch dt.entity.* used standalone or as the primary result sourcesmartscapeNodes is the only valid path. No raw dimension alternative exists.

Decision:

  • Situations 1 or 2 — load references/mass-data-filtering-strategy.md and complete all steps including field discovery (Step 2) and equivalence verification (Step 4). Do not skip the fieldsSnapshot gates — they determine which approach is viable. Only fall back to the Migration Workflow below when the entity-type mapping or relationship traversal is needed to complete a Smartscape subquery.
  • Situation 3 — continue with the Migration Workflow and entity mapping table below.
Note: Situation 3 has a sub-case where classicEntitySelector is used to filter the entities returned by fetch dt.entity.*. This is rare and follows the same smartscapeNodes path — resolve the selector conditions using references/mass-data-filtering-strategy.md Step 1B, then apply them as node filters in smartscapeNodes.

Migration Workflow

Follow this order for Situation 3 (pure entity list queries) and for constructing Smartscape subqueries in Situations 1 and 2:

  1. Identify the classic input pattern:
  • fetch dt.entity.*
  • classicEntitySelector(...)
  • relationship field access such as belongs_to[...], runs[...], instance_of[...]
  • signal or event queries using dt.entity.*
  1. Identify the involved classic entity types.
  2. Look up the Smartscape replacement in the core entity mapping table below.
  3. Check which classic DQL constructs need explicit migration.
  4. Rewrite the query using Smartscape primitives:
  • smartscapeNodes
  • smartscapeEdges
  • traverse
  • references
  • getNodeName()
  • getNodeField()
  1. Check for special cases, unsupported entities, or ID assumptions.
  2. Load the matching detailed references for the specific entity family or migration pattern.

For the full migration process and output expectations, load references/migration-workflow.md.

Core Entity Mapping Table

Use this compact table first for common migrations. For the full mapping set, load references/type-mappings.md.

Classic / Gen2 entitySmartscape fieldSmartscape node typeNotes
dt.entity.hostdt.smartscape.hostHOSTStandard host mapping
dt.entity.servicedt.smartscape.serviceSERVICEStandard service mapping
dt.entity.process_group_instancedt.smartscape.processPROCESSProcess instance maps directly
dt.entity.container_group_instancedt.smartscape.containerCONTAINERContainer-group instance maps directly
dt.entity.kubernetes_clusterdt.smartscape.k8s_clusterK8S_CLUSTERKubernetes cluster
dt.entity.kubernetes_nodedt.smartscape.k8s_nodeK8S_NODEKubernetes node
dt.entity.kubernetes_servicedt.smartscape.k8s_serviceK8S_SERVICEKubernetes service
dt.entity.cloud_applicationmultiple workload fieldsmultiple K8S workload node typesMaps to multiple workload types; load the cloud-application guide
dt.entity.cloud_application_instancedt.smartscape.k8s_podK8S_PODClassic cloud app instance becomes pod
dt.entity.cloud_application_namespacedt.smartscape.k8s_namespaceK8S_NAMESPACENamespace mapping
dt.entity.applicationdt.smartscape.frontendFRONTENDFrontend application mapping
dt.entity.aws_lambda_functiondt.smartscape.aws.lambda_functionAWS_LAMBDA_FUNCTIONCloud-function entity mapping

DQL Constructs to Inspect During Migration

These classic constructs usually need explicit rewriting:

Classic constructTypical Smartscape replacementNotes
entityName(x)name or getNodeName(x)Prefer name when querying nodes directly
entityAttr(x, "...")direct node field or getNodeField(x, "...")Prefer direct fields when available
classicEntitySelector(...)node filters plus traverseStart from the constrained side; for mass data queries see mass-data-filtering-strategy.md first
dt.entity.* in signal queriesdt.smartscape.*Applies to by, filter, fieldsAdd, expand, and related clauses
belongs_to[...], runs[...], instance_of[...]traverse or references[...]references works only for static edges
classic entity ID filtersSmartscape idDo not reuse classic IDs blindly
affected_entity_ids and affected_entity_typessmartscape.affected_entitiesOne record array replaces the two parallel arrays; each record has id, type, and name

For the detailed function-by-function guide, load references/dql-function-migration.md.

Special Cases

Do not translate these patterns literally:

  • Host group — no standalone Smartscape entity; use fields on HOST
  • Process group — no standalone Smartscape entity; use fields on PROCESS
  • Container group — no standalone Smartscape entity; preserve output shape with placeholders if needed
  • Classic IDs — classic entity IDs do not carry over to Smartscape automatically
  • Planned, missing, or not-planned mappings — check the full mapping table before assuming direct support

Load references/special-cases.md before migrating these patterns.

Entity-Focused Guides

When a migration centers on a specific entity family, load the matching detailed guide:

Each guide explains:

  • what the classic entity represented
  • what the Smartscape replacement is
  • which fields usually change
  • how relationships are migrated
  • common examples and pitfalls

References

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
dynatrace
Comunidade

dt-obs-frontends

Real User Monitoring (RUM) on Dynatrace — web and mobile frontends. Core Web Vitals, user sessions, page performance, mobile crashes, frontend errors, and frontend-backend linking. Query via user.events, user.sessions, and dt.frontend. metrics. Does NOT cover synthetic monitoring (HTTP/browser/network checks) — that's a separate domain.

Instalações / 1h
1
GitHub Stars
181
Atualizado
9 de nov.
dynatrace
Comunidade

dt-obs-logs

Log querying, filtering, pattern analysis, and error rate calculation. Use when searching application or infrastructure logs, analyzing error patterns, or correlating log data. Trigger: "show error logs", "search logs for keyword", "log error rate", "recent errors", "logs from last hour", "find log entries", "top error messages", "log patterns", "parse JSON logs", "logs by process group", "log trends over time", "log entry counts per minute". Do NOT use for explaining existing queries, product d

Instalações / 1h
1
GitHub Stars
181
Atualizado
9 de nov.
dynatrace
Comunidade

dt-sec-contextualization

Resolve security signals, IoC matches, or Smartscape nodes to runtime entities, connect findings across entity levels, verify external findings against RVA on the same entity, and measure scan coverage against a Smartscape denominator. Covers identity mapping, RVA id resolution, K8s pod vs. node CVE topology, AI-service vulnerabilities, coverage counts. Trigger: "map these findings to workloads/hosts", "which workload does this image run as", "is this scanner finding also detected by RVA on a ru

Instalações / 1h
1
GitHub Stars
181
Atualizado
9 de nov.
dynatrace
Comunidade

dt-setup-openinference-migration

Migrate a GenAI/LLM app off Traceloop/OpenLLMetry onto OpenInference with its OTel genai. semconv option enabled (enablegenaisemconv / OPENINFERENCEENABLEGENAISEMCONV). Covers detecting the existing Traceloop setup, swapping the instrumentor per SDK, and the ingestion-shape question that decides what's fixable afterward — an app-owned OTel trace exporter vs. instrumentation-only with OneAgent picking up the spans. Flags that the semconv option is additive, not a replacement — legacy llm./openinf

Instalações / 1h
1
GitHub Stars
181
Atualizado
9 de nov.