Releases
See what changed. Catch what came back.
Attach release information to telemetry, compare application versions and connect regressions to the code your team shipped.
Use one release identifier
Set a consistent release value in your SDK configuration and deployment workflow. That links incoming telemetry to a version your team recognises.
Follow regressions
A resolved issue can reopen when the error returns. Investigate the affected release, occurrence and session instead of starting from a fresh, unrelated report.
Read the surrounding change
Repository context can support the investigation where configured. Commit and release information provide evidence; they do not prove that a particular commit caused the error.
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.