Update entity queries

Latest Dynatrace
How-to guide
4-min read

What changes

In Latest Dynatrace, Synthetic monitors and locations are represented as Smartscape nodes instead of Classic entities. Existing Dashboards, alerts, SLOs, Notebooks, and automation that use Classic entity types or IDs must be updated before the corresponding Classic fields are retired.

Build the dependency inventory

Use the Classic entity model usage in DQL section of the upgrade readiness dashboard as the primary inventory source. It lists every dashboard, notebook, workflow, anomaly detector, and SRG that has executed a query referencing Classic entity constructs, including all dt.entity.synthetic.* types, with direct links to each document.

The dashboard reflects recent query executions. Dormant or archived documents that have not been opened or run recently will not appear. For complete coverage, also export or inspect dashboards, notebooks, alert rules, SLO definitions, and automation, and search their source for the Classic entity type names listed below.

Classic Synthetic entity types to search for:

dt.entity.synthetic_test
dt.entity.http_check
dt.entity.multiprotocol_monitor
dt.entity.synthetic_location
dt.entity.external_synthetic_test

Create one work item for every match, recording the object owner, original query, replacement query, and regression-test result.

Rewrite queries

For the mapping of Classic entity types to Smartscape node types and DQL examples, see Synthetic monitors in Smartscape.

For each document identified in the inventory

Open the document and locate queries using fetch dt.entity.synthetic_* or referencing Classic entity IDs.
Rewrite each query using the Smartscape node types and attributes.
For alert rules, verify that the entity selector field does not reference a Classic entity type.
For SLOs, confirm the SLO recalculates correctly on the migrated query.
Save the object and confirm that its result is consistent with the previous version for the agreed comparison period.

Record the replacement query and a passing regression test for every inventoried object.

Build the dependency inventory

Classic Synthetic entity types to search for:

dt.entity.synthetic_test
dt.entity.http_check
dt.entity.multiprotocol_monitor
dt.entity.synthetic_location
dt.entity.external_synthetic_test

Create one work item for every match, recording the object owner, original query, replacement query, and regression-test result.

Rewrite queries

For the mapping of Classic entity types to Smartscape node types and DQL examples, see Synthetic monitors in Smartscape.

For each document identified in the inventory

Open the document and locate queries using fetch dt.entity.synthetic_* or referencing Classic entity IDs.
Rewrite each query using the Smartscape node types and attributes.
For alert rules, verify that the entity selector field does not reference a Classic entity type.
For SLOs, confirm the SLO recalculates correctly on the migrated query.
Save the object and confirm that its result is consistent with the previous version for the agreed comparison period.

Record the replacement query and a passing regression test for every inventoried object.

Update entity queries

What changes

Build the dependency inventory

Rewrite queries

Related topics

Update entity queries

What changes

Build the dependency inventory

Rewrite queries

Related topics