Engineering
How to structure a log
Good logs are not just messages. They are small, queryable events with stable names, scalar attributes, and enough context to debug production systems.
Engineering
MongoDB Query Tracing in .NET with Sentry + OTLP
Learn how to trace MongoDB queries in your .NET apps using OpenTelemetry instrumentation and Sentry's OTLP support, with full correlation to errors and replays.
Engineering
Your agent should understand what you see
Seer Agent now understands Sentry pages through structured semantic context instead of ASCII snapshots, cutting token usage by up to 85% while maintaining the same answer quality.
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.
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.
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.
Engineering
From vibe code to production-ready: observability for Next.js and Supabase apps
Supabase gives you query insights and logs, but it can't trace across your full stack. Here's how to connect Next.js, Supabase Edge Functions, and Postgres with distributed tracing, log drains, and AI-assisted debugging in Sentry.
Engineering
Fixing JavaScript observability, one library at a time
Sentry is adding TracingChannel support to 44 JavaScript libraries upstream, replacing fragile monkey-patching with native observability that works across all runtimes.
Engineering
When agents orchestrate agents, who's watching?
Multi-agent AI systems fail silently. Learn what proper observability looks like when agents orchestrate agents, and how Sentry keeps you in control.
