Engineering
When and what should I be logging?
When in doubt, start by adding a few targeted log lines. Here are best practices for using logs to make your application easier to debug.
Engineering
Any Apple update can break our app. Here's how we find out first.
After 1.6 million downloads, the Usage app team shares how they use Sentry's crash monitoring, error tracking, size analysis, and user feedback to stay ahead of Apple platform changes.
Engineering
Reading the agent traces is how you make the call your eval can't
Picking a model for your agent is a tradeoff between cost, quality, and speed. Here's a free-tier model that made things up, what an eval would and wouldn't have caught, and why reading the agent traces is how you actually decide.
Product Updates
Signal: The key to Self-Healing Software
More code is shipping faster than ever, and most of it is no longer written by people. The speed is the story everyone tells. What matters more is what happens after the code ships, where software is starting to notice it is broken, understand why, and write the fix itself.
Engineering
Next.js already traces your requests. Here's how to export them with OpenTelemetry.
Next.js already creates traces for your requests. With @vercel/otel and a couple environment variables, you can export them to any OTLP-compatible backend.
Product Updates
Better, faster, less wrong: Enhancing issue grouping
We trained and deployed a new issue grouping model that prevents 20% more duplicate issues, halves incorrect merges, and makes future model upgrades trivial.
Product Updates
Catch visual regressions with Snapshots, now in beta
Sentry Snapshots is in beta. Diff screenshots on every commit, block the PR if there are visual changes, and use snapshots as context for AI agents.
Engineering
Works on my machine: how we use AI to reproduce reported bugs
Sentry's SDK team uses a Claude skill to automatically set up reproduction environments for bug reports, cutting hours of boilerplate setup to minutes.
Engineering
Errors, traces, logs, metrics: when to reach for what
Errors, traces, logs, and metrics overlap more than you'd think. An opinionated, practical guide to which signal to reach for, and why the choice decides what you (and your coding agents) can debug later.
Engineering
How we cut build times by two-thirds by deleting our CMS
Sentry replaced its legacy headless CMS with Astro, Markdown, and AI-driven automation — cutting build times from 14 minutes to under 4 and eliminating broken builds.
Engineering
You don’t need to pick one: how Sentry and OpenTelemetry work together
Teams with existing OpenTelemetry instrumentation do not need to choose between OTel and Sentry. Keep OTel on the backend, use the Sentry SDK on the frontend, and export OTLP events to Sentry.
Engineering
Your agent can't fix what it can't see
The bottleneck for self-healing software isn't agent intelligence. It's that agents have no idea what actually broke in production. Sentry MCP and the CLI bridge that gap.
Product Updates
The product analytics you already have
You already have everything you need. Your Sentry traces, logs, and metrics can answer most product analytics questions without a separate tool.
Product Updates
New ways to agentically build and edit dashboards
Sentry dashboards just got a major upgrade: create dashboards with AI agents, manage them via the CLI, and clone pre-built templates for common monitoring use cases.
