Skip to main content

RUM

RUM shows what real browsers experience on your sites: Core Web Vitals, views, and JavaScript errors. Like APM it is opt-in per site.

Enabling RUM​

  • Sites on your instrumented hosts: open RUM and enable the site from the candidates list. Nothing is added to the site itself; the snippet is injected automatically and beacons flow through the host's agent. See RUM on the agent side for how that works. A site whose PHP pool runs a version the injector cannot work with (below 8.1), or whose pool overrides the injection point, is left out of the candidates list on purpose, because enabling it there would collect nothing; such a site takes the custom-site path below.
  • Any other site (hosted elsewhere, or a runtime the injector does not cover): Custom site asks for the domain and shows a one-line <script> tag to paste into the page. The site starts reporting the moment the tag is live. If such a site later moves onto an instrumented host, the automatic path takes over by itself and the manual tag can be removed whenever convenient; nothing double-counts.

A custom site's detail page keeps showing the snippet (with a copy button) until the first views arrive, so the tag is never lost.

Reading the site page​

  • Visitor pulse: views over 24 hours on the card, and view/LCP charts on the detail page, with day pinning.
  • Core Web Vitals: p75 values with the good/needs-improvement/poor bands.
  • Pages: top paths by views with per-page timings. Where a page view carried a trace, a trace button jumps straight into the APM waterfall of that exact request.
  • Audience: countries, browsers, device classes. Only a country is ever stored; visitor IPs are dropped at ingest.
  • Errors: JavaScript errors with source locations, including unhandled promise rejections. An error storm on a site raises an incident (a built-in rule).
  • Friction: rage clicks and error clicks, counted per element, so "visitors keep hammering the buy button and it throws" is a row, not a support ticket. Errors carry breadcrumbs: the last navigations and network requests (with status where the browser exposes it) leading up to the error. No session recording is involved, only counters, selectors and a short structured trail. See what is collected.

Switching off​

The Manage block on the site's detail page switches RUM off: collection and billing stop, history remains. For a custom site, remove the snippet from the page too.