Sessions
The steps before the exception.
Explore an ordered event timeline for a visit, connecting page views, interactions and errors without recording a user's screen.
Reconstruct the journey
Follow the recorded actions leading up to a problem. A session gives an exception a place in the user experience instead of leaving it as an isolated stack trace.
Carry context across the investigation
Use a stable internal user identifier when cross-session analysis is needed. Release, device and environment context help narrow the investigation.
A timeline, not a recording
ErrorDock sessions are telemetry event timelines. They are not video recordings or DOM replay. Review what your application sends and avoid including sensitive input in event properties.
Related
- Find the failure. Keep the context. Group exceptions into issues, inspect stack traces and breadcrumbs, and understand which users and releases are affected.
- Fix what matters to your users. Bring errors, performance and feature usage together to help prioritise engineering work by its effect on the product.
Bring your application into focus.
Tell us about your stack. We will help define the right beta setup for your first project.