In our daily lives as developers, we have to deal with a lot of code that we did not write ourselves (or wrote ourselves but already forgot that we did). We use tons of libraries that make our lives easier because they deal with complex stuff like machine learning, time zones, or printing. As a result, much of the code base we work with on a daily basis is a black box to us. But there are times when we need to learn what is happening in that black box.

Users are complaining about slow load times and you’ve thrown logs, traces, and metrics — heck, the entire kitchen sink of performance monitoring — at your application, but you still can’t figure out the source of the bottleneck. Maybe you missed adding instrumentation to something in the critical path, or you’re simply testing in an environment vastly different from the ones your users are experiencing in production.

As a developer, triage duty week was often the worst week of my month. Anytime a bug was reported, I’d search for the right environment, wander through logs, pray there was an associated stack trace, use my mental mapping of our code base, and route bugs to the right teams. Developers on triage rotation need to ensure bugs are routed to the correct team along with adequate information to help the team investigate the bug.

Building high quality, performant mobile apps is hard. Developers need to keep up with rapidly changing technologies, high user expectations, and competitive app stores. We sat down with Julius Skripkauskas and Walt Leung to discuss how mobile developers can build better mobile experiences, including choosing the right technology, focusing on the right KPIs, and staying on top of trends in device formats and AI.

You run an e-commerce website and notice a drop in sales on a specific product page. You suspect that users may be encountering an issue with the “Add to Cart” button, but you’re not sure what’s causing the problem. With Sentry Session Replay’s new search by user click feature, you can easily find replays where users clicked on that button and watch their sessions to see exactly what happened.

If you have a large codebase with multiple developers shipping quickly – errors need to be caught quickly as well. To help ensure your code is performant and reliable while you’re deploying code, we partnered with GitHub to build a bridge between your CI/CD workflow and your favorite error monitoring tool (Sentry, of course).

Today we’re announcing our new Spend Allocation feature and updates to Spike Protection, giving you more control over how your projects consume events. While we’ve made it super easy for teams to add Sentry to their projects, we kept hearing from the community that they wanted more guardrails to ensure their noisy projects don’t eat through their event quota.

Today is a special day at Sentry, as today we welcome Syntax to the family. We’ve long been fans of Scott and Wes, of what they’ve built with Syntax, and of their general curiosity, drive, and hustle. As one of Sentry’s earliest partners, it’s been amazing to watch and experience their growth alongside our own. Today we’re going to talk about the next chapter of Syntax, one with increasing ambition, and one we hope you’ll be just as excited about as we are.

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.