|
By Paul Jaffre
You used to monitor services. Then you started monitoring AI calls inside services. Now your AI agent is spinning up other AI agents to complete tasks. Your old monitoring instincts need to evolve. This isn't hypothetical. Agentic architectures are already in production. Coding agents are calling search agents; orchestrators are spawning specialized sub-agents for retrieval, planning, and execution. Teams are shipping these systems faster than they're figuring out how to watch them.
|
By Sigrid Huemer
Almost every production application uses a number of different tools and libraries,whether that’s a library to communicate with a database, a cache, or frameworks like Nest.js or Nitro. To be able to observe what’s going on in production, application developers reach out for Application Performance Monitoring (APM) tools like Sentry. But there’s an inherent problem: the performance data that APM tools need is most often not coming natively from the libraries themselves.
|
By Sergiy Dybskiy
I've been building a multi-agent research system. The idea is simple: give it a controversial technical topic like "Should we rewrite our Python backend in Rust?", and three agents work on it. An Advocate argues for it, a Skeptic argues against, and a Synthesizer reads both briefs blind and produces a balanced analysis. Each agent has its own model, its own tools, its own system prompt. It worked great in testing. Then I noticed the Synthesizer kept producing analyses that leaned heavily toward one side.
Native crashes on Android have always been harder to debug than they should be. The platform has its own crash reporter (debuggerd) that captures the crashing thread, every other running thread, register state, and memory maps into a file called a tombstone. Tombstones have been a part of Android for a long time; in fact, they’ve been there in one form or another since Android's first commit.
|
By Sergiy Dybskiy
A little while ago, when agents were telling me “You’re absolutely right!”, I was building webvitals.com. You put in a URL, it kicks off an API request to a Next.js API route that invokes an agent with a few tools to scan it and provide AI generated suggestions to improve your… you guessed it… Web Vitals. Do we even care about these anymore?
|
By Sergiy Dybskiy
Most "agent observability best practices" content reads like a compliance checklist from 2019 with "AI" pasted over "microservices." Implement comprehensive logging. Establish evaluation metrics. Create governance frameworks. Not a single line of code. No mention of what happens when your agent silently picks the wrong tool on turn 3 and you need to figure out why.
|
By James W.
You spent months instrumenting your app with OpenTelemetry. The idea of ripping it out to adopt a new observability backend is not an option. Sentry's OTLP endpoint means you don't have to. In fact, two environment variables are all you need and your existing traces start showing up in Sentry's trace explorer. Sentry's OTLP support is currently in open beta. This means you can start using it today, but there are some known limitations we'll cover later.
|
By Kyle Tryon
A typical Next.js deployment can execute code in up to three different runtimes: Edge, Node.js, and the browser. You may already be capturing logs from server-side code, but if you are not capturing the full request from middleware through server rendering to the browser, you are missing a lot of debugging info when things go wrong. TL;DR: A typical Next.js deployment can run in up to three environments; Node, Edge, and the browser.
|
By Sergiy Dybskiy
This blog is based on a recent live workshop. You can watch the the full livestream on Youtube. Next.js gives you a lot for free; server-side rendering, file-based routing, edge runtimes. What it doesn’t give you is a clear picture of what’s actually happening in production.
|
By Kush Dubey
Seer is our AI agent that takes bugs and uses all of the context Sentry has to find the root cause and suggest a fix. We use it all the time to help us improve Sentry. Seer fixes Sentry. More recently, Seer has been helping us fix itself — Seer fixing Seer. An upstream outage triggered a bit of an avalanche, revealing a bug that had been hiding away for months. When it came time to fix it, Seer pointed us exactly where we needed to look.
|
By Sentry
We've published Sentry pre-built dashboards that are free and extensible! Check them out!
|
By Sentry
No signup form. No dashboard. No copy-pasting DSNs. Sentry is now a provider on Stripe Projects, which means you can provision a fully configured Sentry project — error monitoring, tracing, and session replay — straight from the CLI in two commands. In this demo, we walk through the full workflow: initializing a project, provisioning Sentry, upgrading and downgrading plans, using magic login to jump straight into your dashboard, and letting a coding agent (Claude Code) handle it all for you.
|
By Sentry
We've published Sentry pre-built dashboards that are free and extensible! Check them out!
|
By Sentry
Seer, Sentry's AI debugger, automatically analyzes your issues and finds the root cause. Now you can pass that analysis directly to a Claude agent - a managed agent session in the Claude Console at platform.claude.com. Once it's done, a link to the branch appears in Sentry so you can review and merge the PR. This video walks through how the integration works and how to set it up in under two minutes.
|
By Sentry
Building AI applications? There's a lot more to monitor beyond errors. With tracing enabled, Sentry's built-in AI Dashboards give you deep visibility into how your agents are actually performing. This video walks through three key dashboard views: You'll also see how to drill from a dashboard widget straight into the trace explorer to pinpoint the root cause of errors, how to duplicate and customize dashboards to fit your needs, and how to set up monitors with alert thresholds - like getting notified if your LLM calls exceed 20 seconds.
|
By Sentry
Use Sentry's Seer Agent to ask anything you need to know about your application. Use Seer Agent to: Email seer@sentry.io for access.
|
By Sentry
We released a new type of dashboard widget - Text Widgets! You can use them to explain other widgets (good for onboarding), or even define your playbooks - instructions on how to investigate failures by reading the other widgets. They even support markdown!
|
By Sentry
Cursor Automations + Sentry Triggers: go from user feedback to a pull request automatically. See how to set up an end-to-end workflow that turns feedback into code changes, posts the PR to Slack, and keeps your team in the loop. In this video, we walk through a real-world example using Sentry Docs. A user submits feedback through a widget on the docs site, it lands in Sentry as an issue, and when assigned, a Cursor Automation kicks off. The automation reads the feedback, validates it, generates a PR against the repo, and posts the link in the relevant Slack thread. No manual work required.
|
By Sentry
Most observability stacks aren’t designed, they accumulate. A logging tool here, a tracing platform there, and before you know it you’re managing rising costs and a setup that ultimately slows down your team. And you’ve moved further away from actually solving problems for your users.
|
By Sentry
Building with Next.js and using Sentry? Our team put together a dedicated Next.js Overview Dashboard that gives you a full picture of your application's health, not just errors. Out of the box, the dashboard covers page loads, API latency, issue counts, performance scores, rage and dead clicks, and slow SSR. Since Next.js runs on both client and server, you get a breakdown of client transactions, server transactions, and your SSR file tree all in one place.
- April 2026 (27)
- March 2026 (12)
- February 2026 (11)
- January 2026 (24)
- December 2025 (10)
- November 2025 (15)
- October 2025 (8)
- September 2025 (21)
- August 2025 (13)
- July 2025 (12)
- June 2025 (15)
- May 2025 (18)
- April 2025 (15)
- March 2025 (14)
- February 2025 (17)
- January 2025 (9)
- December 2024 (13)
- November 2024 (15)
- October 2024 (9)
- September 2024 (11)
- August 2024 (21)
- July 2024 (19)
- June 2024 (10)
- May 2024 (11)
- April 2024 (9)
- March 2024 (23)
- February 2024 (6)
- January 2024 (11)
- December 2023 (12)
- November 2023 (15)
- October 2023 (7)
- September 2023 (14)
- August 2023 (7)
- July 2023 (11)
- June 2023 (10)
- May 2023 (9)
- April 2023 (7)
- March 2023 (13)
- February 2023 (15)
- January 2023 (8)
- December 2022 (13)
- November 2022 (10)
- October 2022 (11)
- September 2022 (16)
- August 2022 (13)
- July 2022 (18)
- June 2022 (12)
- May 2022 (19)
- April 2022 (13)
- March 2022 (11)
- February 2022 (16)
- January 2022 (2)
- December 2021 (7)
- November 2021 (9)
- October 2021 (5)
- September 2021 (12)
- August 2021 (10)
- July 2021 (6)
- June 2021 (9)
- May 2021 (14)
- April 2021 (9)
- March 2021 (8)
- February 2021 (14)
- January 2021 (5)
- December 2020 (6)
- November 2020 (12)
- October 2020 (5)
- September 2020 (5)
- August 2020 (5)
- July 2020 (14)
- June 2020 (12)
- May 2020 (6)
- April 2020 (3)
- March 2020 (4)
- February 2020 (13)
- January 2020 (3)
- December 2019 (4)
- November 2019 (7)
- October 2019 (4)
- September 2019 (12)
- August 2019 (6)
- July 2019 (5)
- June 2019 (5)
- May 2019 (8)
- April 2019 (11)
- March 2019 (8)
- February 2019 (11)
- January 2019 (8)
- December 2018 (3)
- November 2018 (4)
- October 2018 (7)
- September 2018 (10)
- August 2018 (8)
- July 2018 (9)
- June 2018 (6)
- May 2018 (4)
- March 2018 (1)
- December 2017 (1)
- November 2017 (1)
- May 2016 (1)
Open-source error tracking that helps developers monitor and fix crashes in real time. Iterate continuously. Boost efficiency. Improve user experience.
Sentry provides open source error tracking that gives you insight into every crash in your stack as it happens, with the details needed to prioritize, identify, reproduce, and fix each issue. Sentry supports all popular languages and platforms, and offers a perspective that enables you to see which errors are doing the most harm to your business and help you understand how issues affect your bottom line.
Find out about exceptions right away. Set up Sentry in minutes with just a few lines of code. Get notifications via email, SMS, or chat as part of an existing workflow when errors occur or resurface.
Quickly find and fix production errors. Triage, reproduce, and resolve errors with max efficiency and visibility. Exception handling with Sentry helps developers build better apps and iterate faster.
See the impact of each release. Integrate error tracking with your commit and deploy workflows. Aggregate events to see where bugs happen, how often, and who's affected before users even notice.
Error tracking built for community. Sentry started as and remains a 100% open-source project, now delivered as a hosted service. Development aligns to security, observability, and production at scale.
Users and logs provide clues. Sentry provides answers.