Code Mappings connect errors to the source code in a repository. And since errors can have paths that are different from the tree structure of the repository, Code Mappings determines the accurate path through a combination of a repository URL and a path transformation.
Sentry uses Code Mappings to serve issue context on the issue details page.
You shouldn’t need a Ph.D. in your APM tool to understand the performance of your application.
Sentry’s new approach to application monitoring is focused on being actionable, affordable, and *is actually* built for developers. Learn how we're redefining the future of APM.
Implementing the right processes and tooling is key to bring your application’s performance from ‘adequate’ to ‘delightful’. Find out how to treat performance as a feature.
We’re making Session Replay generally available to all Sentry users. Remove the guesswork from troubleshooting by seeing video-like reproductions of what users experience leading up to and after an error or performance issue. Session Replay supports all web-based platforms.
Stack traces show us exactly where an exception occurred, but you can still be left wondering: What arguments or state caused the exception to occur?
If you can reproduce the issue locally with a debugger attached you’ll have access to these local variables, but with Sentry you can identify the exception location *without* needing to reproduce the issue locally. By including local variables with stack traces, Sentry events become much closer to the full debugging experience.