01
RUM
Session explorer and event timeline
Browse sessions by user, geography, browser, duration, and error count, then inspect ordered views, actions, requests, and errors.
Product · RUM & Session Replay
See the user journey that happened before the backend failed.
Connect browser sessions, actions, errors, Web Vitals, and frontend requests to the same trace and time context used by backend telemetry. Reproduce the journey in Session Replay, then continue into the responsible backend span.
- real-user sessions
- RUM
- reconstructed journeys
- Replay
- field performance
- Web Vitals
- frontend → backend context
- trace_id
Frontend evidence, connected to the incident.
Move from an affected user or slow page to the exact replay moment, frontend request, and backend trace without rebuilding context.
02
Performance
Web Vitals and frontend API performance
Track LCP, FID, CLS, and TTFB alongside API volume, p50/p95 latency, and error rate for real browser traffic.
03
Errors
Error tracking with source maps
Group JavaScript errors by fingerprint, count impacted users, inspect affected sessions, and map minified frames back to source.
04
Correlation
Session-to-trace correlation
Use W3C trace context carried by RUM actions to open the backend trace, with time correlation as a fallback.
05
Ownership
Replay data on your object storage
Keep replay events and their ordered session metadata on infrastructure you control, alongside the rest of your telemetry.
06
Session Replay
Interactive replay and privacy controls
Reconstruct the page, jump between views, actions, errors, and requests, skip inactivity, adjust playback speed, and apply sampling and masking controls.
workflow
From a browser symptom to the responsible backend span.
The useful unit is not a video alone. It is the replay moment, browser event, error, request, and backend trace kept in one investigation.
- 101 · Capture
Receive sessions, actions, errors, and replay events
Use the browser SDK to configure collection, sampling, and privacy policy while preserving trace context on frontend requests.
- 202 · Prioritize
Find slow or error-heavy experiences
Filter real sessions and use Web Vitals, error rate, affected users, and frontend API latency to choose where to investigate.
- 303 · Reconstruct
Replay the journey at the failure
Reconstruct the page and jump directly to the views, actions, errors, and network requests surrounding the issue.
- 404 · Correlate
Open the backend trace without copying IDs
Carry the session window and trace context into the request path, service, logs, metrics, and profiles.
proof / shipped
One frontend investigation, end to end.
RUM, Session Replay, error tracking, performance, source maps, and trace correlation share one session and time context.
- Search real sessions and affected users
- Replay the exact journey around an error or slow request
- Resolve minified JavaScript frames with source maps
- Continue from the browser request into the backend trace
Product · RUM & Session Replay
See the user journey that happened before the backend failed.
Connect browser sessions, actions, errors, Web Vitals, and frontend requests to the same trace and time context used by backend telemetry. Reproduce the journey in Session Replay, then continue into the responsible backend span.