dt-migration

To convert Dynatrace classic entity DQL queries to Smartscape equivalents, you rewrite classic entity types into Smartscape node types and map classic selectors to Smartscape traversal patterns. This ensures your queries follow current Smartscape DQL syntax rules.

Migrating classic entity selectors to Smartscape DQL involves mapping functions like entityName(), entityAttr(), and classicEntitySelector() to Smartscape traversal equivalents. This transition ensures compatibility with Smartscape node types and relationship patterns.

Yes, you need a solid understanding of Dynatrace DQL syntax and structure to perform classic entity conversion. The migration process relies on recognizing classic entity types and rewriting them into valid Smartscape DQL patterns.

Yes, you can map classic relationship patterns directly to Smartscape traversal in DQL. This conversion handles classic entity relationships and ensures the migrated queries maintain compatibility with Smartscape node structures.

The best way to transition Gen2 entity-based structures to Smartscape is by converting classic entity types to Smartscape node types and rewriting DQL patterns. Loading a migration skill before writing your final DQL ensures seamless mapping.

Migrated Dynatrace DQL queries often fail in Smartscape due to unmapped classic entity selectors or outdated syntax. You must rewrite classic entity types and relationship patterns to match Smartscape traversal equivalents for successful execution.