Session Replay

Get to the root cause of an issue faster by watching replays of real user sessions in Sentry with best-in-class privacy controls. Understand when, where, and how an error is impacting your app without having to repro it yourself, talk to a customer, or exposing sensitive data.

Loading image for Debug with visual context media
Loading image for Protect your users' privacy media
Loading image for See user frustration signals in the UX media

Visual Debugging for Developers

Navigate your application’s console output, network calls, and even inspect your application’s DOM tree. It’s like having your browser’s dev tools right inside Sentry.

Lock down your debugging experience without sacrificing user privacy with a range of privacy controls to ensure no sensitive user information leaves the browser.

See dead clicks and rage clicks in the Replay view to understand where users are getting stuck.

Getting Started Platforms Scrolling Logo Background
Getting Started Platforms Scrolling Logo Background
Getting Started Platforms Scrolling Logo Background
Getting Started Platforms Scrolling Logo Background
Getting Started Platforms Scrolling Logo Background
Getting Started Platforms Scrolling Logo Background

Getting started with Sentry is simple

We support every technology (except the ones we don't).
Get started with just a few lines of code.

Install

The Replay integration is already included in your browser or framework SDK NPM packages. If you’re using CDN bundles instead of NPM packages, you need to load the Replay integration CDN bundle in addition to your browser bundle:

Click to Copy
npm install --save @sentry/browser

Set Up

To set up the integration, add the following to your Sentry initialization. There are several options you can pass to the integration constructor. See the configuration documentation for more details.

Click to Copy
// import Sentry from your framework SDK (e.g. @sentry/react) instead of @sentry/browser import * as Sentry from "@sentry/browser"; Sentry.init({ dsn: "https://examplePublicKey@o0.ingest.sentry.io/0", // This sets the sample rate to be 10%. You may want this to be 100% while // in development and sample at a lower rate in production replaysSessionSampleRate: 0.1, // If the entire session is not sampled, use the below sample rate to sample // sessions when an error occurs. replaysOnErrorSampleRate: 1.0, integrations: [ Sentry.replayIntegration({ // Additional SDK configuration goes in here, for example: maskAllText: true, blockAllMedia: true, }), ], });

Session Replay supports all browser-based applications. This includes static websites, single-page-applications and also server-side-rendered, that includes frameworks such as: Django, Spring, ASP.NET, Laravel, Express and Rails.

Click to Copy
<script src='https://js.sentry-cdn.com/examplePublicKey.min.js' crossorigin='anonymous' ></script>

FAQs

Sentry’s Session Replay provides a video-like reproduction of user interactions on a site or web app, giving developers the details they need to resolve errors and performance issues faster. All user interactions - including page visits, mouse movements, clicks, and scrolls - are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI.

Session Replay supports all web applications whether it’s static or dynamic, server-side rendered or single-page applications.

It is built to work with @sentry/browser, and our browser framework SDKs:

This means Session Replay is supported on server-side rendered Web applications such as Express, Laravel, Rails, Django, ASP.NET, Sprint Boot and others. We recommend creating a separate project in Sentry to track frontend errors from your backend. And adding Session Replay to your frontend via npm, or using the loader.

You will be able to set up Session Replay with only a few lines of code. Your existing @sentry/browser basic setup + DSN can be used for configuration.

Session Replay has minimal impact on the performance on your web application. We employ standard optimizations such as data compression, which is performed in a web worker outside of the browser’s UI thread in such a way that minimizes impact on your application. You can measure the overhead of Session Replay on your application without deploying to production by following these instructions.

We offer a range of privacy controls to ensure that no sensitive user information leaves the browser. By default, our privacy configuration is very aggressive and masks all text and images, but you can – for example – choose to just mask user input text. More on that can be found in our documentation. We also provide server-side scrubbing to additionally filter on the server in case anything slips by.

Additionally, we offer a self-serve deletion capability of individual replays in the UI.

Session Replay adheres to the same security standards and is subject to the same compliance requirements as all of our software. Please see our Security page for further details.

Please check out our pricing page for details.

Of course we have more content

Get monthly product updates from Sentry

Sign up for our newsletter.

And yes, it really is monthly. Ok, maybe the occasional twice a month, but for sure not like one of those daily ones that you just tune out after a while.

By filling out this form, you agree to our privacy policy. This form is protected by reCAPTCHA and Google's Privacy Policy and Terms of Service apply.

Fix it

Get started with the only application monitoring platform that empowers developers to fix application problems without compromising on velocity

© 2024 • Sentry is a registered Trademark of Functional Software, Inc.