A stack trace tells you where the code failed. A session replay shows what the visitor did to get there: the pages they opened, where they clicked, and what the page looked like at that moment. Monocle plays the session back with its requests and errors on the same timeline, so you can go from a click to the backend trace it triggered.
Session replay is in beta. Email julien@monocle.sh to turn it on for your account.
See what led to an error
Each browser error recorded during a session gets a Replay tab on its issue occurrence. It starts a few seconds before the error, so you see the clicks and requests that led to it. Monocle links the recording to that exact occurrence, never by time or by user, so the replay you watch is the session that failed.
In the player, each request links to its trace and each error links to its issue. One session connects the frontend, the backend, and the error.
Record only what you need
Replays come from the replay() integration of the browser SDK. Nothing records until the visitor consents and your code calls grantConsent().
By default, the SDK records 10% of consenting sessions in full. The other sessions keep their last 60 seconds in the browser and upload them only when an error happens. You get a replay for most errors without paying for every session.
Input values are masked by default. Visible text and images are recorded, unless you mask them with maskAllText or mark sensitive parts of the page. Review a test recording before you turn replay on for your visitors.
Retention and limits
- Monocle keeps recordings for 30 days. Members with manager access can delete one earlier.
- Free and Trial include 100 recordings per month, Starter 1,000, and Business 5,000. A recording counts once, when it starts, and deleting it doesn't restore the quota.
- When the organization runs out of recordings and replay budget, new recordings stop until the next usage period. Errors, logs, and traces keep flowing.
- A recording stops after 60 minutes.
See session replay billing for prices.