1. Measuring the back/forward cache with Application Metrics (blog.sentry.io)
A bfcache hit leaves no trace in ordinary metrics. Here's how Sentry's bfcacheMetricsIntegration makes back/forward cache health measurable.
2. Building Sentry's Laravel AI Integration (blog.sentry.io)
How we built zero-config Agent Tracing for Laravel AI, from AI code review to matching LLM calls with HTTP requests.
3. Debugging our AI search assistant with agent tracing (blog.sentry.io)
See how Sentry engineers used AI Conversations to debug a natural language search assistant and fix a tricky query generation bug.
4. Application Metrics caught my broken size estimator (blog.sentry.io)
The numbers your app lives on don't belong in logs or on sampled spans. Here's how a browser video converter's KPIs made the case for Application Metrics.
5. From one switch to a control panel: meet `dataCollection` (blog.sentry.io)
Sentry SDKs replace the `sendDefaultPii` boolean with `dataCollection`, granular options for user data, headers, bodies, GenAI data, and more.
6. How to evaluate session replay software: a developer's guide (blog.sentry.io)
Compare session replay tools on recording methodology, privacy architecture, integration depth, overhead, AI-readability, and mobile support
7. Automated agent triage with Agent Tracing and Claude Routines (blog.sentry.io)
How Sentry uses a Claude Routine and the Sentry MCP to automatically triage 800 AI agent conversations overnight and file bugs.
8. What's new in Sentry Logs: The summer 2026 roundup (blog.sentry.io)
Everything that shipped for Sentry Logs this summer: log pinning, JSONL exports, terabyte-scale search, and a dozen usability improvements.
9. How we built an automated debugging workflow at Sentry (blog.sentry.io)
How Sentry uses Seer autofix and Claude routines to build an automated debugging workflow that detects, fixes, and routes code issues automatically.
10. Your OTel spans, our errors: A Sentry love story in one trace (blog.sentry.io)
The OtlpIntegration bridges OTel traces and Sentry errors. Keep your OTel setup, add Sentry for errors, and see both in one trace waterfall.
11. Session Replay for Unreal Engine: see the crash before the crash (blog.sentry.io)
The Sentry Unreal Engine SDK now records the last seconds of gameplay and attaches the footage to crash reports, so you can watch what led to the crash.
12. From 57 bugs to 1, thanks to Seer (blog.sentry.io)
Learn how to automate bug fixes using Sentry, Seer, and cloud coding agents to clear your backlog.
13. .NET support for Godot is now generally available (blog.sentry.io)
Sentry's Godot Engine SDK 2.0.0 brings C#/.NET error reporting and application metrics to general availability.
14. How to structure a log (blog.sentry.io)
A practical guide to writing structured, queryable, lint-enforceable logs with consistent event names, attributes, severity, and schema checks.
15. MongoDB Query Tracing in .NET with Sentry + OTLP (blog.sentry.io)
Trace MongoDB queries in .NET using OpenTelemetry and Sentry's OTLP ingestion. See spans, query data, and error correlation in Sentry.
16. Your agent should understand what you see (blog.sentry.io)
How Sentry replaced ASCII page snapshots with structured semantic context to make Seer Agent faster, cheaper, and ready for agentic actions.
17. When and what should I be logging? (blog.sentry.io)
Learn logging best practices: what to log, how to structure messages, and what to avoid. Practical tips with Sentry's structured logging.
18. Any Apple update can break our app. Here's how we find out first. (blog.sentry.io)
How the Usage app uses Sentry to catch crashes, silent errors, and build regressions before 1.6 million users notice.
19. Reading the agent traces is how you make the call your eval can't (blog.sentry.io)
I gave the free tier a cheaper model and it invented conference speakers who don't exist. What that taught me about model tradeoffs, evals, and reading agent traces.
20. Next.js already traces your requests. Here's how to export them with OpenTelemetry. (blog.sentry.io)
Next.js creates OpenTelemetry traces automatically. Learn how to export them to Sentry or any OTLP backend with @vercel/otel.
21. Better, faster, less wrong: Enhancing issue grouping (blog.sentry.io)
Sentry's new AI grouping model prevents 20% more duplicate issues while cutting incorrect merges in half. Here's how we trained and deployed it.
22. Catch visual regressions with Snapshots, now in beta (blog.sentry.io)
Sentry Snapshots is now in beta. Get screenshot diffing in CI to catch unintended visual changes on every commit, for any platform with a frontend.
23. Works on my machine: how we use AI to reproduce reported bugs (blog.sentry.io)
How Sentry's SDK team built a Claude skill to auto-reproduce bug reports, reducing triage time across 159 packages.
24. Errors, traces, logs, metrics: when to reach for what (blog.sentry.io)
Errors, traces, logs, and metrics overlap enough that it's hard to know which to use. Here's when to reach for each signal, with a real debugging walkthrough.
25. How we cut build times by two-thirds by deleting our CMS (blog.sentry.io)
Sentry replaced its CMS with Astro, Markdown, and Claude Code skills β cutting build times from 14 to under 4 minutes and eliminating API failures.
26. You donβt need to pick one: how Sentry and OpenTelemetry work together (blog.sentry.io)
Use Sentry on the frontend, keep OpenTelemetry on the backend, and choose direct OTLP or Collector forwarding for OTLP events.
27. Your agent can't fix what it can't see (blog.sentry.io)
Agents can't fix bugs they can't see. Learn how Sentry MCP and CLI give coding agents the production context to diagnose and fix issues automatically.
28. The product analytics you already have (blog.sentry.io)
Your Sentry traces, logs, and metrics already answer most product analytics questions. Learn how to query existing telemetry for product insights.
29. New ways to agentically build and edit dashboards (blog.sentry.io)
Create and edit Sentry dashboards with AI agents, the Sentry CLI, or pre-built templates you can clone and customize for your monitoring needs.
30. From vibe code to production-ready: observability for Next.js and Supabase apps (blog.sentry.io)
Instrument Next.js and Supabase with Sentry to get unified errors, distributed traces, logs, performance insights, and AI-assisted fixes.