Operations | Monitoring | ITSM | DevOps | Cloud

Sentry

AMA: Getting Started with OpenTelemetry and Sentry

Join the Sentry developers who built Sentry’s OpenTelemetry support and learn how to understand the performance of your OTel instrumented applications. As the leading open standard for observability, thousands of companies use OpenTelemetry to capture data across their services - but capturing raw logs, traces, and metrics is only the first step in improving software performance.

AMA: Making Code Performance More Actionable

To eliminate hours of manual triage and analysis for your code performance degradations, join the engineers who are building Sentry’s performance product, Alex and George, as they share how to use Sentry to see and solve your critical app performance issues immediately. During this livestream, the team will dive into Sentry Performance Issues – which tells you exactly what’s slow in your code – so you can take action and solve latency problems without combing through dashboards and playing guess-a-span.

New Performance Issues | Snack of the Week

We’ve released new Performance Issues for Frontend, Backend, and Mobile recently. N+1 API Calls, Large Render-blocking Assets, and Slow Database Queries are just a few of them. If you want to learn more, you can register for our upcoming Performance Issues AMA where you can talk with the engineers who built our performance product: .

Code Mappings and Why They Matter

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.

Making Performance Monitoring More Actionable with Sentry

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.