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.
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.
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.
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.
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.
Sentry is adding TracingChannel support to 44 JavaScript libraries upstream, replacing fragile monkey-patching with native observability that works across all runtimes.
Multi-agent AI systems fail silently. Learn what proper observability looks like when agents orchestrate agents, and how Sentry keeps you in control.
Monkey-patching in CJS and module hooks in ESM both instrument libraries from the outside. Tracing Channels let libraries emit their own telemetry — and the ecosystem is already moving.
When an agent's tool call silently degrades the input to a completely different agent two steps later, standard monitoring won't catch it. Here's how to find bugs that live between agents.
Most discussions about agent observability read like outdated compliance checklists with "AI" substituted for older technologies. They emphasize comprehensive…
How Sentry's AI debugging tool Seer helped identify and fix a cascading region blocklist bug that caused an outage in Seer's own EU deployment.
Do you need an MCP to build your native app? Surprisingly, modern agents succeed either way. The real difference is how much time, cost, and context you waste along the way.
Replace Any with type-safe protocols, handle array conformance limitations, and future-proof your Swift enums.
Explore protocol extensions, enums with associated values, and ExpressibleByStringLiteral to build type-safe Swift APIs.
How to hook pure Swift functions at runtime using an in-process debugger.