RUM Workflow

The general workflow of Edge Inserted RUM (EIR) is as follows:

How to

  1. An end user requests a RUM-enabled Web page, and that page has been randomly selected to have RUM dimension and metric data collected. The page is selected based on the configured sampling rate.
  2. An Edge Server serves the RUM-enabled Web page, which includes a small, non-blocking JavaScript wrapper.
    The JavaScript wrapper requests the RUM JavaScript used to collect timing data, loads the RUM JavaScript asynchronously, and sets some initial variables. Sending the JavaScript wrapper first helps further minimize any potential performance impact to the page.
    Note: Origin Inserted RUM (OIR) works slightly different than Edge Inserted RUM (EIR), as OIR includes a sample rate in the JavaScript; the edge server takes no action. For details, see Origin Inserted RUM (OIR) vs. Edge Inserted RUM (EIR)
  3. The JavaScript wrapper requests the RUM JavaScript.
  4. The Edge Server sends the RUM JavaScript to the end user’s device.
  5. After the RUM JavaScript executes on the end user’s device, it:
    • Determines whether the device supports Navigation Timing
    • Collects performance data using Navigation Timing
  6. The browser:
    • Sends or beacons, the data to an Edge Server
    • Receives a 204 No Content HTTP response from the Edge Server
  7. The Intelligent PlatformTM processes and stores the data for visualization within the portal.
  8. When requested, the portal queries the back-end to get the data needed for customer reports.