Operations | Monitoring | ITSM | DevOps | Cloud

Using a transformer-based text embeddings model to reduce Sentry alerts by 40% and cut through noise

Sentry uses Issue Grouping to aggregate identical errors and prevent duplicate issues from being created, and duplicate alerts being sent. One of the chief complaints we’ve heard from our users is that in some cases the existing algorithm did not sufficiently group similar errors together, and Sentry would create separate issues and alerts, causing unnecessary disruption–or at least annoyance–to developers.

Find and Fix Performance Bottlenecks with Sentry's Trace Explorer

We’ve all worked on that app that hangs just a little too long in weird places, or had that query we could never get to perform just right. The network waterfall in Chrome DevTools can’t quite show us what’s going on behind the scenes, and tracing with OTel (and honestly, tracing in Sentry) was just… hard. Today that changes.

Introducing the Sentry Trace Explorer

The Trace Explorer is a new way to query and visualize the application metrics from the traces and spans within your applications. In this video, Cody from the Sentry Developer Experience team shows you how you can get started using it. Want to dive in and find your slow database queries, or what pages or components are loading the slowest? Trace Explorer is the best way to do it - and gives you an easy path to jumping into the spans that make up all actions within your application.

A Guide to Logging and Debugging in Java

During the development of your program, you might rely on simple println() statements to trace program execution flows and identify issues in your code. But as projects grow in size and complexity, print statements quickly become messy. A better approach to tracing program execution is logging, an approach that provides a consistent and organized way to track your application’s behavior, allowing you to systematically identify and resolve issues.

Sentry's Pinia Integration for Vue and Nuxt Error Tracking

When debugging issues in production, context is everything. While Sentry already provides rich error data like stack traces, breadcrumbs, and user information, understanding the application state at the time of an error can still help reproduce, fix and ship quickly. Sentry’s Pinia integration solves this by automatically capturing Pinia state wherever errors occur. Now you get the complete picture of your Vue or Nuxt application's state at the moment things went wrong.

Smarter Tools and Best Practices for Mobile Debugging: A Hands-On Workshop

You get a crash report: “App crashed on checkout page.” But you can’t reproduce it on your Pixel. Maybe it’s only happening on a Samsung device? Maybe it’s a memory issue? Or maybe the user was on a bad network? Now you’re stuck digging through logs, guessing at settings, and running the same scenario over and over in your emulator.

Session Replay for Mobile is now Generally Available: See What Your Users See

Session Replay for Mobile is now generally available. I could bombard you with hyperbolic statements about why Session Replay is worth using, but instead, A…I… wrote you a haiku: Screen freeze, devs all sigh. Replay uncovers the crime: Forgot.addListener.