Updates to Synthetic attribute names

  • Latest Dynatrace
  • Reference
  • 3-min read
  • Page has not been published yet
Only relevant for DPS licensing

This change affects only DPS tenants, for which Synthetic generates Grail events.

In January 2025, we renamed some of the Synthetic event attributes to align Synthetic events with latest Dynatrace naming conventions. This specifically affects batch_status events produced by, for example, Synthetic for Workflows.

If your workflows use output from Synthetic for Workflows, check your workflows and update all instances of the old attribute names.

You have until May 31, 2025, to make these updates:

  • Until May 31, 2025, Synthetic for Workflows returns attributes in both the old and new naming formats.
  • After May 31, 2025, Synthetic for Workflows will return attributes only in the new naming format.

A comparison of all old and new names is provided in the table below.

How to update attribute names

Because Synthetic for Workflows output can be used in so many ways across different workflow actions, it is not possible to automatically update attribute names. Therefore, you'll need to find and update all affected attribute names manually.

To find affected attribute names, open each workflow and look for any instances of the old attribute names in the workflow actions.

  • Look at all workflow tasks that follow a Synthetic for Workflows action (that is, tasks that could use the results of the Synthetic for Workflows action).
  • You'll find Synthetic attribute names in the action's configuration pane, under the Input and Conditions tabs.

However, to be sure, look through all possible configuration options for each workflow. Update the attribute name according the table below and then save the workflow. Do this for all workflows.

Comparison of old and new names

This table includes all affected batch_status event attributes, with old attribute names and the corresponding new attribute names.

Further information about Synthetic batch_status events (attribute, type, description, and examples) is available at Synthetic batch status.

__key__ and __index__ are placeholders; the exact values depend on the specific Synthetic for Workflows action.

Old attribute name
New attribute name
dt.synthetic.batch.status
batch.status
dt.synthetic.result.duration
batch_result.duration
dt.synthetic.result.executed_count
batch_result.executed_count
dt.synthetic.result.failed_count
batch_result.failed_count
dt.synthetic.result.failed_to_execute_count
batch_result.failed_to_execute_count
dt.synthetic.result.total_duration
batch_result.total_duration
dt.synthetic.result.triggered_count
batch_result.triggered_count
dt.synthetic.result.triggering_problems_count
batch_result.triggering_problems_count
dt.synthetic.configuration.fail_on_performance_issue
configuration.fail_on_performance_issue
dt.synthetic.configuration.fail_on_ssl_warning
configuration.fail_on_ssl_warning
dt.synthetic.configuration.processing_mode
configuration.processing_mode
dt.synthetic.configuration.take_screenshot_on_success
configuration.take_screenshot_on_success
dt.synthetic.metadata.__key__
metadata.__key__
dt.synthetic.triggered_executions
triggered_executions
dt.synthetic.failed_executions.__index__.location.id
failed_executions.__index__.dt.entity.synthetic_location
dt.synthetic.failed_executions.__index__.monitor.id
failed_executions.__index__.dt.synthetic.monitor.id
dt.synthetic.failed_executions.__index__.execution.end_timestamp
failed_executions.__index__.execution.end_timestamp
dt.synthetic.failed_executions.__index__.execution.id
failed_executions.__index__.execution.id
dt.synthetic.failed_executions.__index__.execution.stage
failed_executions.__index__.execution.stage
dt.synthetic.failed_executions.__index__.status.code
failed_executions.__index__.result.status.code
dt.synthetic.failed_executions.__index__.status.details
failed_executions.__index__.result.status.details
dt.synthetic.failed_executions.__index__.status.message
failed_executions.__index__.result.status.message
dt.synthetic.failed_executions.__index__.status.on_demand.message
failed_executions.__index__.result.status.on_demand.message
dt.synthetic.failed_to_execute.__index__.location.id
failed_to_execute.__index__.dt.entity.synthetic_location
dt.synthetic.failed_to_execute.__index__.monitor.id
failed_to_execute.__index__.dt.synthetic.monitor.id
dt.synthetic.failed_to_execute.__index__.execution.end_timestamp
failed_to_execute.__index__.execution.end_timestamp
dt.synthetic.failed_to_execute.__index__.execution.id
failed_to_execute.__index__.execution.id
dt.synthetic.failed_to_execute.__index__.execution.stage
failed_to_execute.__index__.execution.stage
dt.synthetic.triggering_problems.__index__.location.id
triggering_problems.__index__.dt.entity.synthetic_location
dt.synthetic.triggering_problems.__index__.entity.id
triggering_problems.__index__.triggering_problem.entity.id
dt.synthetic.triggering_problems.__index__.cause
triggering_problems.__index__.triggering_problem.cause
dt.synthetic.triggering_problems.__index__.details
triggering_problems.__index__.triggering_problem.details
Related tags
Digital Experience