builtin:rum.resource-timing-origins)
OneAgent uses the Server-Timing
response header to communicate RUM correlation data to the Real User Monitoring JavaScript. In case of cross-origin requests, the RUM JavaScript can only access the value of the Server-Timing
header if the Timing-Allow-Origin
header allows its origin to do so.
Add rules to restrict resource-timing information access to only defined origins. If not already set by your application, OneAgent will automatically add the Timing-Allow-Origin
header to the response of your web application, thereby granting all origins access to resource timing details.
builtin:rum.resource-timing-origins
group:web-and-mobile-monitoring.web-applications
group:web-and-mobile-monitoring
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:rum.resource-timing-origins |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:rum.resource-timing-origins | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:rum.resource-timing-origins |
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.
matcher
EQUALS
STARTS_WITH
ENDS_WITH
CONTAINS
pattern