Control RUM at the process group level

Latest Dynatrace
How-to guide
Published Apr 01, 2026

By default, RUM is enabled for all process groups. For the technologies listed in Technology support - Real User Monitoring - Web servers and applications, this allows OneAgent to do the following:

Automatically inject the RUM JavaScript into each page delivered by this process group; see Configure automatic injection in the New RUM Experience.
Deliver the RUM JavaScript; see Configure the Real User Monitoring code source in the New RUM Experience.
Handle beacon requests; see Configure the beacon endpoint for web frontends in the New RUM Experience.
Add the Server-Timing response header required to establish frontend-to-backend linking for page loads. This allows you to drill down from the page load waterfall to distributed traces.

You can disable RUM for a process group, for example, to exclude servers that don't require RUM monitoring. Disabling RUM for a process group can also serve as a workaround for application issues. However, we recommend contacting a Dynatrace product expert via live chat to help determine the root cause.

Disable RUM for a process group

If you disable RUM for a process group, all RUM functionality listed above is turned off.

To disable RUM for a process group

Go to Settings.
In the upper-left corner of the page, select Go to entity, and then select the process group you want to configure.
Go to Collect and capture > Real User Monitoring.
Turn off Enable Real User Monitoring.

Important considerations

If you prefer to insert the RUM JavaScript manually, do not turn off RUM for your process groups to suppress injection. Doing so suppresses not only the injection, but all RUM functionality listed above. Instead, use a custom injection rule as described in Use manual insertion for pages of an auto-injected frontend.
If you want to roll out RUM in a selective manner after deploying OneAgent on your hosts, we recommend using the approach described in Roll out RUM selectively for your frontends in the New RUM Experience. In principle, the RUM enablement setting at the process-group level also allows for a selective rollout, but this tends to be complex and error-prone.