Code coverage insights - now in your stack trace
I’m Jerrod, the Head of Codecov @ Sentry. I’d like to share updates from the first major release of our Codecov and Sentry integration and new Codecov pricing for Sentry customers.
I’m Jerrod, the Head of Codecov @ Sentry. I’d like to share updates from the first major release of our Codecov and Sentry integration and new Codecov pricing for Sentry customers.
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.
How your code performs isn’t a subjective debate. Well, at least not anymore — in the past few months, Sentry has started telling you exactly what’s slow and where to fix it — specifically, N+1 database queries in your code. While we’ve all had to fix an N+1 problem, performance problems come in multiple flavors. Today, you’ll notice more Performance Issues in your issue feed, Slack alerts, and email notifications.
The observability landscape - specifically your traditional Application Performance Monitoring (APM) offerings are failing modern-day developers. These legacy tools are made for ops and infra teams to keep their infrastructure and services up and running. But when it comes to helping the people that actually write the code to find and fix latency issues, these tools - which often come with massive price tags - leave developers hunting for issues causing slowdowns.