Transition from RUM Classic to the New RUM Experience

Latest Dynatrace
Explanation
1-min read

If you already monitor your web and mobile frontends with RUM Classic, upgrading to the New RUM Experience is straightforward. Learn how the New RUM Experience relates to RUM Classic and how to enable it.

Enable the New RUM Experience

Upgrading from RUM Classic to the New RUM Experience requires only a configuration change. The following guides outline the necessary steps.

Relationship between the New RUM Experience and RUM Classic

The New RUM Experience currently relies on certain RUM Classic functionalities. Here’s what this means for you.

Dependence on RUM Classic

You can currently enable the New RUM Experience only if RUM Classic is active. At this time, disabling data ingestion into RUM Classic and fully migrating is not possible.

Configuration

Most configuration settings for the New RUM Experience are based on those already used by RUM Classic. This means that:

Changes made in the New RUM Experience also apply to RUM Classic.
Conversely, if you modify settings in RUM Classic that are also available in the New RUM Experience, those changes will apply there as well.

Event and session properties are an exception—they have a separate configuration from user action and session properties in RUM Classic.

Monitoring traffic

When the New RUM Experience is enabled, RUM beacons in a new format are sent alongside RUM Classic beacons to the same endpoint.

Infrastructure requirements

The New RUM Experience relies on the same HTTP headers and cookies as RUM Classic. If your firewalls or other infrastructure components are already configured to comply with the firewall constraints for RUM Classic, no additional configuration is typically required to support the firewall constraints for the New RUM Experience.

An exception is the handling of the beacon URL query string. In the New RUM Experience, its integrity is verified using a checksum. Your infrastructure must therefore ensure that the beacon URL query string is not altered in any way—this includes the modification, removal, or reordering of parameters.

Identify issues caused by an altered beacon query string

If you followed one of the guides in Enable the New RUM Experience, but Experience Vitals shows no data or less data than expected, check whether your infrastructure is modifying the beacon query string.

Identify beacons of the new format

To identify RUM beacons, open the network tab of your browser's developer tools and look for requests with the URL path /bf or requests where the last URL path segment starts with rb_. Then check their query strings—beacons in the new format include the query string parameter pv=4.

Check the beacon response

Beacon requests of the new format rejected by the beacon endpoint return a JSON response with the field status set to ERROR.

They also include the fields errorCode and errorReason. If the query string was altered, you will see one of the following combinations:

3014—Query string CRC mismatch
3001—Parameter ty missing

Built-in metrics

The New RUM Experience provides numerous built‑in metrics. Due to its different underlying data model, these are not direct equivalents of the RUM Classic metrics. Still, many metrics have functional replacements, which are listed in RUM metrics upgrade.