Try it free

Enable RUM for your Classic web applications

  • Latest Dynatrace
  • How-to guide

If you already monitor your web frontends with RUM Classic, upgrading to RUM requires only a configuration change. This guide outlines the prerequisites and necessary steps.

Prerequisites

Before enabling RUM, make sure the following conditions are met.

  • RUM Classic is enabled at the level—frontend or environment—where you want to enable RUM.
  • The RUM JavaScript version is RUM JavaScript version 1.329+. Because new features are added regularly, we recommend updating it automatically as described in Configure the RUM JavaScript version for a frontend.
  • The snippet format code snippet, which is not supported by RUM, isn't used. For alternatives, see Recommendations for selecting the snippet format.
  • The OneAgent version is OneAgent version 1.301+. We recommend keeping OneAgent up to date, as new features are added regularly. For full frontend-backend linking functionality, including support for the Server-Timing header, OneAgent version 1.331+ is required.
  • Your infrastructure complies with the infrastructure pass-through requirements. If it's already configured for RUM Classic, no additional adjustments are typically required, except in cases where the beacon URL query string is altered; see Transition from RUM Classic to RUM.

Enable RUM for a web frontend

To enable RUM for a web frontend

  1. Go to Experience Vitals Experience Vitals > Overview.
  2. Select Web to view all web frontends.
  3. Select the frontend you want to configure.
  4. Switch to the Settings tab.
  5. Under Enablement and cost control, turn on RUM.
  6. Optional If you want to capture user interactions such as clicks and scrolls, enable User Interactions.

If you use automatic injection, the new configuration is applied within 5 minutes. If you insert the RUM JavaScript manually, you may need to update the snippet, depending on the snippet format you’re using:

  • JavaScript tag: The new configuration is applied automatically, but it may not take effect immediately due to caching. The file that contains the monitoring code and configuration is cached for one hour on the Dynatrace CDN. Additionally, browsers respect the configured cache duration.
  • OneAgent JavaScript tag, OneAgent JavaScript tag with SRI or inline code: As with any configuration change, you need to update the inserted snippet.

If your frontend is receiving traffic, the charts in Experience Vitals Experience Vitals should begin showing data within minutes after the configuration takes effect. If no data appears, verify that the prerequisites are met.

Enable RUM at the environment level

To enable RUM for web frontends at the environment level

  1. Go to Settings Settings > Collect and capture > Real User Monitoring > Traffic and cost control > Web frontends.
  2. Turn on Enable Real User Monitoring. Note that this setting is displayed only if Enable Real User Monitoring Classic is enabled; see Prerequisites.

For more information on how the new configuration propagates and when you need to update a manually inserted snippet, see Enable RUM for a web frontend.

Enable RUM via API

The Settings API allows you to enable RUM either for a web frontend or at the environment level. For details, see Settings API - Enablement and cost control schema table.

Unless you use the JavaScript tag snippet format, you need to update the snippet after you've enabled RUM if it was manually inserted. For more information, see Enable RUM for a web frontend. To retrieve the updated snippet, use the RUM manual insertion tags API.

Related topics

  • Transition from RUM Classic to RUM
Related tags
Digital Experience