RUM Resources inherit from all the context related to the active RUM View at the time of collection.
To get even more complete, end-to-end visibility into requests as they move across layers of your stack, connect your RUM data with corresponding backend traces. This enables you to:
See Connect RUM and Traces for information about setting up this feature.
Detailed network timing data for resources is collected from the Fetch and XHR native browser methods and from the Performance Resource Timing API.
|number||Entire time spent loading the resource.|
|number (bytes)||Resource size.|
|number (ns)||Time spent establishing a connection to the server (connectEnd - connectStart).|
|number (ns)||Time spent for the TLS handshake. If the last request is not over HTTPS, this metric does not appear (connectEnd - secureConnectionStart).|
|number (ns)||Time spent resolving the DNS name of the last request (domainLookupEnd - domainLookupStart).|
|number (ns)||Time spent on subsequent HTTP requests (redirectEnd - redirectStart).|
|number (ns)||Time spent waiting for the first byte of response to be received (responseStart - RequestStart).|
|number (ns)||Time spent downloading the response (responseEnd - responseStart).|
Note: If you are having trouble collecting detailed timing for some resources, see Resource timing and CORS.
|string||The type of resource being collected (for example, |
|string||The HTTP method (for example |
|number||The response status code.|
|string||The resource URL.|
|string||The host part of the URL.|
|string||The path part of the URL.|
|object||The query string parts of the URL decomposed as query params key/value attributes.|
|string||The protocol name of the URL (HTTP or HTTPS).|
|string||The resource provider name. Default is |
|string||The resource provider domain.|
|string||The resource provider type (for example |
RUM infers the name and category of the resource provider from the resource URL host part. If the resource URL host matches the current page URL host, the category is set to
first party. Otherwise, the category will be
social for example.
The Resource Timing API is used to collect RUM resource timing. It is subject to the cross-origin security limitations that browsers enforce on scripts. For example, if your web application is hosted on
www.example.com and it loads your images via
images.example.com, you will only get timing for resources loaded hosted on
www.example.com by default.
To resolve this, enable extended data collection for resources subject to CORS by adding the
Timing-Allow-Origin HTTP response header to your cross-origin resources. For example, to grant access to the resource timing to any origin, use
Timing-Allow-Origin: *. Find more about CORS on the MDN Web Docs