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. Upgrade readiness for Latest Dynatrace requires RUM JavaScript version 1.347+.
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 Upgrade data capturing.
Enable RUM for a web frontend
To enable RUM for a web frontend
Go to Experience Vitals > Overview.
Select Web to view all web frontends.
Select the frontend you want to configure.
Switch to the Settings tab.
Under Enablement and cost control, turn on RUM.
Optional If you want to capture user interactions such as clicks and scrolls, enable User Interactions.
Enable RUM at the environment level
To enable RUM for web frontends at the environment level
Go to Settings > Collect and capture > Real User Monitoring > Enablement and cost control > Web.
Turn on RUM. Note that this setting is accessible only if RUM Classic is enabled; see Prerequisites.
If you use automatic injection, the new configuration is applied within 5 minutes, and no further action is required. 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 should begin showing data within minutes after the configuration takes effect. If no data appears, verify that the prerequisites are met.