Settings API - Real User Monitoring for process group schema table
Real User Monitoring for process group (builtin:rum.processgroup)
With Real User Monitoring enabled, Dynatrace gathers details about load times and page behavior that your customers experience with your application. Only applications with injected JavaScript tags can be monitored.
| Schema ID | Schema groups | Scope |
|---|---|---|
builtin:rum.processgroup |
| PROCESS_GROUP - Process Groupenvironment |
| GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:rum.processgroup |
| SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:rum.processgroup | |
| Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:rum.processgroup |
Authentication
To execute this request, you need an access token with Read settings (settings.read) scope. To learn how to obtain and use it, see Tokens and authentication.
Parameters
| Property | Type | Description | Required |
|---|---|---|---|
Enable Real User Monitoringenable | boolean | Allows OneAgent to:
If you don't enable this setting, your RUM data may not be correlated with your server-side PurePaths, which will be a problem when the root of the server-side PurePath is captured on this process group. For example, consider an Apache HTTP server as a proxy and a Java app server as a backend. Disabling this setting for the process group of the Apache HTTP server will break the RUM correlation, even if Dynatrace injects the RUM JavaScript tag on the process group of the Java backend. For RUM data to correlate with server-side PurePaths, RUM must be enabled on the OneAgent that instruments the entry point of your application (the Apache HTTP server in this example). | required |