Should you use a log or a metric?
Logs and metrics look nearly identical when you're instrumenting code. Using a signup handler as the example, here's how to tell which question each one answers, and when you can just count the logs.
Logs and metrics look nearly identical when you're instrumenting code. Using a signup handler as the example, here's how to tell which question each one answers, and when you can just count the logs.
Over 40 changes between 8.43.0 and 8.54.0 cut SentryAndroid.init time by 20-30%, reduced memory allocation, fixed memory leaks, and lowered background CPU time.
We moved Android SDK operations to a worker isolate, then streamlined scope updates by removing duplicate normalization and encoding JSON directly into UTF-8 bytes.
Etsy engineering manager Jay Henry on running a code slush instead of a freeze, keeping alert fatigue out of peak season, and pricing a crash in GMS.
The back/forward cache is one of the most impactful performance features on the web and one of the least observable, because success looks like silence. Here's how we made it measurable.
How we built zero-config Agent Tracing for Laravel AI during Agent Hackweek, from AI-generated defensive code to matching LLM calls with HTTP requests.
How our team used Sentry's own AI Conversations feature to debug our natural language search assistant.
Some numbers are too important to bury in a log or lose to sampling. A little video converter became the clearest case I've seen for tracking KPIs with Application Metrics.
Session replay tools split into UX analytics tools and developer debugging tools. Here's how to tell which one you're evaluating, and the architectural questions that matter for each.
Every morning, a Claude Routine reads the previous night's Seer conversations, flags the broken ones, and files Linear tickets — before anyone's at their desk.
We built a system that uses Seer and Claude routines to automatically detect, fix, and route code issues — here's what we built and what we learned.
The OtlpIntegration connects your OpenTelemetry traces with Sentry error tracking, so you can click an error and see the OTel trace that caused it.
Most bugs sit in the backlog forever because fixing them costs more than the feature they compete with. With Sentry, Seer, and cloud coding agents, that math has changed.
Good logs are not just messages. They are small, queryable events with stable names, scalar attributes, and enough context to debug production systems.
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.