Enable browser monitors on latest Dynatrace

• Latest Dynatrace
• How-to guide
• 4-min read
• Updated on Oct 01, 2026

What changes

Enabling Browser monitors on latest Dynatrace makes browser monitor results available in Grail. You can query them with DQL, use them in Dashboards and Notebooks, and view the enhanced Requests waterfall. The feature adds Duration, User events duration, and User events total duration metrics for the complete monitor and for individual steps.

When the environment is upgraded, every browser monitor that doesn't yet run with the latest RUM JavaScript is switched to latest Dynatrace automatically. This doesn't change whether a monitor is enabled or disabled. It changes only how its executions are measured and reported. You don't need to switch every monitor manually. However, switch a representative group before the upgrade so you can verify execution, review duration differences on the readiness dashboard, and adjust thresholds, dashboards, or alerts where needed. After the upgrade, Classic monitoring is no longer available.

Before enabling Browser monitors on latest Dynatrace for a monitor that runs from a private location, confirm that every Synthetic Engine associated with the location is healthy, currently reporting, and runs version 1.347+.

Identify browser monitors not yet on latest Dynatrace

Open the Check your upgrade readiness dashboard. The Browser monitors section shows which monitors are Not migrated, Migrated, or Monitor disabled, and the duration difference for migrated monitors. See Check your upgrade readiness for details.

You can also query directly with DQL:

smartscapeNodes BROWSER_MONITOR
| fields name, id, is_on_latest_dynatrace
| filter is_on_latest_dynatrace == false

Enable the setting

You can switch on the feature per monitor or at environment level.

To switch on the feature for a single monitor:

To switch on the feature at the environment level:

This switches on the feature for all browser monitors that inherit the environment setting. Monitors with an explicit override keep their monitor-level setting.

After switching on the feature, wait for successful executions and review the duration differences on the readiness dashboard. Investigate monitors where the difference is significant and adjust thresholds, dashboards, or alerts where needed. This comparison is only possible while both reporting paths are active.

Compare performance and adjust thresholds

While both Classic and Grail reporting paths are active, compare duration metrics for each monitor and step to identify differences that might require threshold adjustments.

What to compare

This comparison is only relevant for monitors and steps that have performance thresholds configured. To compare at monitor level:

timeseries {
  classic = avg(dt.synthetic.browser.classic.total_duration),
  new = avg(dt.synthetic.browser.user_actions.total_duration)
},
by: { dt.synthetic.monitor.id, dt.synthetic.monitor.name }
| fieldsAdd diff = (abs(new[] - classic[]) / classic[]) * 100
| fieldsAdd avg_classic = arrayAvg(classic) / 1000,
            avg_new = arrayAvg(new) / 1000,
            avg_percentage_diff = arrayAvg(diff)
| fields dt.synthetic.monitor.name, dt.synthetic.monitor.id,
         avg_classic, avg_new, avg_percentage_diff
| filter avg_percentage_diff > 5
| sort avg_percentage_diff desc

To compare at step level:

timeseries {
  classic = avg(dt.synthetic.browser.step.classic.total_duration),
  new = avg(dt.synthetic.browser.step.user_actions.total_duration)
},
by: { dt.synthetic.monitor.id, dt.synthetic.monitor.name,
      dt.synthetic.step.id, dt.synthetic.step.name }
| fieldsAdd diff = (abs(new[] - classic[]) / classic[]) * 100
| fieldsAdd avg_classic = arrayAvg(classic) / 1000,
            avg_new = arrayAvg(new) / 1000,
            avg_percentage_diff = arrayAvg(diff)
| fields dt.synthetic.monitor.name, dt.synthetic.step.name,
         dt.synthetic.step.id, avg_classic, avg_new, avg_percentage_diff
| filter avg_percentage_diff > 5
| sort avg_percentage_diff desc

These queries filter out differences of 5 percent or less. Focus on the remaining monitors and steps where you have performance thresholds configured.

When to adjust thresholds

Small differences (under 5 percent) are expected and typically do not require changes. For monitors where the difference is larger, review the configured performance threshold and adjust it to match the new baseline in Settings > Collect and capture > Synthetic Monitoring > Performance thresholds.

Verify the upgrade

For every monitor you switched, confirm:

Rollback

Before the environment is upgraded, you can switch a monitor back by disabling Browser monitors on latest Dynatrace for that monitor or at environment level. Classic reporting continues uninterrupted.