Getting started with Web RUM: From setup to real insight in 6 steps

Most RUM dashboards show you averages. Embrace shows you real sessions — so you can replay exactly what happened.

You’ll see how stitched sessions combine network requests, logs, Web Vitals, and errors into a single timeline, giving you the full story behind every slowdown or crash.

 ➡️ Docs: Sessions and Timelines

? Quick win: Once you send your first session data, open the Sessions view and click into a timeline — it’s the fastest way to see how Embrace visualizes real user behavior.

Once the SDK is live, Embrace automatically starts collecting page-load performance data and Core Web Vitals — no extra instrumentation required.

Use these views to see how your app performs in the real world.

• Page Load Insights show which resources (JS, CSS, fonts, etc.) affect latency and caching efficiency.
• Core Web Vitals (LCP, CLS, INP) reveal how users experience your pages, with element-level attribution so you know exactly what caused layout shifts or delays.
  

➡️ Docs: Page Load Insights • Core Web Vitals

? Pro tip: Sort the resource table by load time to find blocking assets, then use the “Attribution” panel to pinpoint which element caused the slowdown.

After you’ve explored what comes out of the box, add manual instrumentation to connect user behavior with performance outcomes.

• Logs record high-value events such as “Add to Cart” or “Checkout Started,” with custom attributes for filtering and aggregation.
• Spans measure performance for key operations like API calls or checkout flows, complete with duration percentiles and slow-span thresholds.

Together, logs and spans tie frontend actions → backend performance → user experience.

➡️ Docs: Logs • Traces & Spans

? Quick win: Filter logs by property (e.g., browserName = Chrome) to isolate conditions behind an issue, then open the related span to measure latency and error rate in context.

Every deployment introduces change — and sometimes regressions.

With Release Health, Embrace lets you compare versions side by side to see which releases introduced new exceptions, slower loads, or higher error counts.

 ➡️ Docs: Release Health

? Quick win: Compare your most recent release to the previous one to confirm that key user journeys (like login or checkout) stayed stable.

Every app has its own success metrics. With custom dashboards, you can build widgets for traffic, exceptions, or conversions — and set up alerts to monitor what matters most to your team.

 ➡️ Docs: Custom Dashboards

? Pro tip: Create an alert for when session counts drop below your baseline. It’s an easy way to catch release issues before users report them.

Turn any Embrace widget into a custom metric and send it to Grafana Cloud or another OpenTelemetry-compatible destination.

Forward network spans to trace API calls end-to-end and link frontend behavior to backend performance.

 ➡️ Docs: Custom Metrics • Grafana Integration

? Quick win: Use Grafana backlinks to jump from a chart straight into the corresponding Embrace dashboard view.

Key takeaways

• 100 % of sessions captured for complete context
  
• Automatic instrumentation covers Web Vitals, Exceptions, and App Health
  
• Understand user flows, not just crashes or averages
  
• Built on OpenTelemetry — no vendor lock-in
  

? Watch the full Getting Started with Web RUM webinar →