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.

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.

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.

There’s a common misunderstanding that profiling is only useful for tiny savings that impact infra costs at scale - the so-called “milliseconds matter” approach. But by dogfooding our own profiling tools, we fixed a problem that saved tens of seconds off each user interaction with our AI agent (and for those of you who like math, that’s four orders of magnitude bigger than those milliseconds that matter).

We knew Visual Studio App Center was retiring, but with an official retirement date of March 31, 2025 and today being *checks calendar* 2025 already, it’s time we choose from our App Center alternatives and start migrating over to other tools. Here’s a quick guide with links to other resources that will make the migration a little less painful.

If you’re a developer that uses Sentry and you’re reading this in 2024, stop reading and head to rollback.sentry.io to get your very own Rollback! Just a few weeks ago, we released Sentry Rollback — our first ever year-in-review experience. Think Spotify Wrapped, but for recapping your year as a developer on Sentry.

Snuba, the primary storage and query service for event data that powers Sentry in production, has historically been doing rate limiting under the hood, making it hard to discover and increasing time to resolve customer support requests. This is not something you’d know the specifics of unless you were deep in the Snuba code. But as we triage support questions from customers, one issue tends to pop up: RateLimitExceeded. You got tired of not getting query results.

If you’ve ever been floored by a sub-100ms response time, you’ve likely got caching to thank. Caching is the unsung hero of performance, shaving precious milliseconds off your application’s response time by storing frequently accessed data, avoiding yet another round-trip request to the database or API. Let’s break down how caching works and explore a few common strategies.