Skip to main content
Real User Monitoring (RUM) records web and mobile user experience and connects frontend telemetry with backend observability.

​
Data model

The Browser and Flutter App SDKs send authenticated events to the same write endpoints: The three streams are created on first write. A new deployment therefore shows an empty state until the SDK sends the first event.

​
Overview

Open RUM → Overview to review sessions, users, errors, page performance, and browser or geography breakdowns for the selected time range.

​
Sessions and replay

Sessions lists recent RUM sessions. Open a session to inspect the action timeline, replay events, errors, device context, and related backend traces. Treat replay as sensitive user data. Apply collection controls in the SDK, avoid recording secrets or personal fields, and use the shortest practical retention.

​
Errors, source maps, and symbols

Errors groups recurring JavaScript failures by fingerprint and shows occurrence count, affected users, stack frames, and example sessions. Upload browser source maps or mobile symbols from RUM → RUM settings → Source Maps & Symbols. MoleSignal uses uploaded debug artifacts to restore minified, obfuscated, or native frames. Reading artifact metadata requires streams.read; upload and deletion require streams.configure.

​
Performance

The performance workspace separates:
  • overview trends;
  • Core Web Vitals;
  • frontend error performance;
  • API and resource timing.
API tables expose count, latency percentiles, and error rate by URL. Use the global time range and facets to compare releases, platforms, countries, or views. Browser applications report Core Web Vitals. Flutter applications report time to first render, build, raster, vsync, and slow-frame data. When an action carries W3C traceparent, the action trace_id links directly to backend spans. When a direct id is not available, session detail can search the session time window for related traces. A slow frontend action can link directly to the corresponding service trace, logs, and metrics while preserving investigation context.

​
Permissions

  • rum.write sends RUM events. Application-bound msrum_ tokens grant only this permission for one application.
  • streams.query opens organization RUM views and related queries.
  • streams.read lists debug-artifact metadata.
  • streams.configure uploads or deletes source maps and mobile symbols.

Browser RUM SDK

Install the SDK and send the first browser session.

Flutter App RUM SDK

Monitor Flutter views, taps, errors, resources, rendering, and screen replay.

Source maps & symbols

Restore Browser, Flutter, Android, and iOS error stacks.

Data sampling

Control session and replay volume independently.

Privacy

Define which browser content can leave the user’s device.

Session replay

Record and reconstruct timestamped DOM changes.
Last modified on August 5, 2026