Dt Migration
Map Dynatrace auto-tagging ManagementZone keys to semantic-dictionary fields when migrating tagging rules or aligning observability with mass data and Smartscape.
Overview
dt-migration is an agent skill for the Operate phase that maps Dynatrace auto-tagging keys to semantic-dictionary fields during tagging migration.
Install
npx skills add https://github.com/dynatrace/dynatrace-for-ai --skill dt-migrationWhat is this skill?
- Documents Auto-Tagging Keys → semantic dictionary field mapping for dt-migration
- Explains ManagementZoneDataSourceMeAttribute keys from auto_tagging_attributes.md
- Covers recursive tag rules, cloud vendor tags (aws/azure/gcp.tags.*), and Kubernetes labels
- Notes Dynatrace primary_tags enrichment on mass data versus full Smartscape tag groupings
- HOST section maps keys like HOST_NAME and HOST_DETECTED_NAME to host.name
Adoption & trust: 603 installs on skills.sh; 87 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Dynatrace auto-tagging keys do not line up with semantic dictionary or mass-data fields, so migrations and AI queries return inconsistent entities.
Who is it for?
Solo devops-minded builders maintaining Dynatrace management zones, primary tags, or HOST/SERVICE dictionaries in live environments.
Skip if: Greenfield Android or web apps with no Dynatrace tenant, or teams that only need generic logging without Dynatrace tagging models.
When should I use this skill?
Migrating or aligning Dynatrace auto-tagging keys with semantic dictionary fields and Smartscape or mass-data attributes.
What do I get? / Deliverables
You get an explicit key-to-field mapping table and tagging semantics so migration scripts and management-zone rules target the correct attributes.
- Key-to-field mapping decisions for migration
- Notes on recursive tag rules and primary tag selection
Recommended Skills
Journey fit
Operate is where production telemetry, tagging, and monitoring semantics must stay correct after deploy. Monitoring covers observability schema work—auto-tag keys, primary tags, and HOST/SERVICE alignment—not feature coding.
How it compares
Reference mapping for Dynatrace tagging migration—not a generic OpenTelemetry bootstrap or application APM install guide.
Common Questions / FAQ
Who is dt-migration for?
Builders and small teams operating Dynatrace who must align auto-tagging attributes with the semantic dictionary and Smartscape fields.
When should I use dt-migration?
During Operate monitoring work when refactoring tags, migrating management zones, or debugging mismatched host and cloud label rules in production.
Is dt-migration safe to install?
It is documentation-style guidance; confirm what your agent can access and review the Security Audits panel on this page before use.
SKILL.md
READMESKILL.md - Dt Migration
# Auto-Tagging Keys → Semantic Dictionary Field Mapping Maps every `ManagementZoneDataSourceMeAttribute` key from `auto_tagging_attributes.md` to the most appropriate field defined in this semantic dictionary. **Legend:** - `—` — no direct equivalent exists in the semantic dictionary --- ## Notes Any auto tagging key referring to ``*_TAGS`` uses a rule condition that is itself based on tags. Note that the referenced tags may either be the result of another rule for which a recursive search is then necessary to find the original underlying attribute. Alternatively, the referenced tags may also be imported from the monitored environment like cloud vendor tags/labels, Kubernetes labels/attributes or OneAgent environment variables. Cloud vendor tags have the pattern ``aws/azure/gcp.tags.*`` where Dynatrace supports "primary tags" which is a way to letting customers select custom tags from the source environment and placing them as enriched fields on mass data and top level attributes on smartscape nodes. For example, a selected Kubernetes label ``team:backend`` on a POD becomes ``primary_tags.team:backend``. Smartscape nodes usually contain all collected environment labels and mass data only a selected subset. Smartscape nodes group labels or tags in the structure of the ``tags`` attribute. ## HOST Matching Smartscape Node: HOST | Auto-Tagging Key | Mass Data Field or Smartscape Node Attribute | |---|---| | `HOST_NAME` | `host.name` | | `HOST_DETECTED_NAME` | `host.name` | | `HOST_AWS_NAME_TAG` | `aws.tags.name` or ``tags:aws[name]``| | `HOST_ONEAGENT_CUSTOM_HOST_NAME` | `host.name` | | `HOST_TAGS` | See above general notes | | `HOST_IP_ADDRESS` | `host.ip` | | `HOST_OS_TYPE` | `os.type` | | `HOST_OS_VERSION` | `os.version` | | `HOST_ARCHITECTURE` | `os.architecture` | | `HOST_BITNESS` | `process.bitness` | | `HOST_CLOUD_TYPE` | `cloud.provider` | | `HOST_HYPERVISOR_TYPE` | — | | `HOST_PAAS_TYPE` | `cloud.platform` | | `HOST_PAAS_MEMORY_LIMIT` | `host.physical.memory` | | `HOST_TECHNOLOGY` | — | | `HOST_CPU_CORES` | `host.logical.cpu.cores` | | `HOST_LOGICAL_CPU_CORES` | `host.logical.cpu.cores` | | `HOST_CUSTOM_METADATA` | — | | `HOST_KUBERNETES_LABELS` | `tags:k8s.labels[<label_key>]` to be found on K8S_NODE *not* on the HOST | | `HOST_AZURE_WEB_APPLICATION_HOST_NAMES` | `azure.container_app.hostname` | | `HOST_AZURE_WEB_APPLICATION_SITE_NAMES` | `azure.site_name` | | `HOST_AZURE_COMPUTE_MODE` | `azure.resource.type` | | `HOST_AZURE_SKU` | — | | `HOST_AIX_VIRTUAL_CPU_COUNT` | `host.virtual.cpus` | | `HOST_AIX_LOGICAL_CPU_COUNT` | `host.logical.cpus` | | `HOST_AIX_SIMULTANEOUS_THREADS` | `host.simultaneous.multithreading` | | `HOST_BOSH_NAME` | — | | `HOST_BOSH_INSTANCE_ID` | — | | `HOST_BOSH_INSTANCE_NAME` | — | | `HOST_BOSH_AVAILABILITY_ZONE` | `aws.availability_zone` | | `HOST_BOSH_DEPLOYMENT_ID` | — | | `HOST_BOSH_STEMCELL_VERSION` | — | | `HOST_GROUP_NAME` | `dt.host_group.id` | | `HOST_GROUP_ID` | Formerly `dt.entity.host_group` but must now be resolved under `dt.host_group.id` representing the plaintext identifier on which the classic entity was based on. | | `GOOGLE_COMPUTE_INSTANCE_ID` | `gcp.instance.id` | | `GOOGLE_COMPUTE_INSTANCE_NAME` | `gcp.resource.name` | | `GOOGLE_COMPUTE_INSTANCE_MACHINE_TYPE` | `gcp.resource.type` | | `GOOGLE_COMPUTE_INSTANCE_PUBLIC_IP_ADDRESSES` | `host.ip` | | `GOOGLE_COMPUTE_INSTANCE_PROJECT` | `gcp.organization.name` | | `GOOGLE_COMPUTE_INSTANCE_PROJECT_ID` | `gcp.project.id` | --- ## PROCESS_GROUP Matching Smartscape Node: Does not exist, attributes need to be found on PROCESS nodes | Auto-Tagging Key | Semantic Dictionary Field | |---|---| | `PROCESS_GROUP_NAME` | `dt.process_group.detected_name` | | `PROCESS_GROUP_DETECTED_NAME` | `dt.process_group.detected_name` | | `PROCESS_GROUP_TAGS` | See above general notes | | `PROCESS_GROUP_LISTEN_PORT` | `process.listen_ports` | | `PROCESS_GROUP_TECHNOLOGY` | — | | `PROCESS_GROUP_TECHNOLOGY_EDITION` | — | | `PROCESS_GROUP_TECHNOLO