--- title: "Introducing Seer Agent: The answer is already in Sentry. Now you can ask for it." sha256: 523b4f6cf1996d739c44d7cc5ca2eb9f286b37dd84a14e7814a3c85ea48da0a7 type: raw-article tags: [sentry,seer-agent,debugging,llm] source: newsletter source_url: https://blog.sentry.io/introducing-seer-agent/ url: https://blog.sentry.io/introducing-seer-agent/ review_value: 7 review_confidence: 8 review_recommendation: worth-reading review_stars: 3 ingested: 2026-05-16 --- # Introducing Seer Agent: The answer is already in Sentry. Now you can ask for it. Title: Introducing Seer Agent: The answer is already in Sentry. Now you can ask for it. URL Source: https://blog.sentry.io/introducing-seer-agent/ Published Time: 2026-04-28T07:00 Markdown Content: # Introducing Seer Agent: The answer is already in Sentry. Now you can ask for it. | Sentry Blog [Skip to main content](https://blog.sentry.io/introducing-seer-agent/#main-content) [](https://sentry.io/welcome/) Menu Platform Products * [Error Monitoring](https://sentry.io/product/error-monitoring/) * [Logs](https://sentry.io/product/logs/) Seer * [Seer NEW](https://sentry.io/product/seer/) * [Agent NEW](https://sentry.io/product/seer/agent/) * [Autofix NEW](https://sentry.io/product/seer/autofix/) * [AI Code Review NEW](https://sentry.io/product/seer/ai-code-review/) * [Session Replay](https://sentry.io/product/session-replay/) * [Metrics NEW](https://sentry.io/product/metrics/) * [Tracing](https://sentry.io/product/tracing/) * [Profiling](https://sentry.io/product/profiling/) * [Size Analysis](https://sentry.io/product/size-analysis/) * [Cron Monitoring](https://sentry.io/product/cron-monitoring/) * [Uptime Monitoring](https://sentry.io/product/uptime-monitoring/) Integrations * [![Image 1](https://blog.sentry.io/astro-assets/nav-icons/github.png)Github](https://sentry.io/integrations/github/) * [![Image 2](https://blog.sentry.io/astro-assets/nav-icons/slack.png)Slack](https://sentry.io/integrations/slack/) * [Sentry CLI](https://cli.sentry.dev/) * [Sentry MCP](https://mcp.sentry.dev/) * [All Integrations](https://sentry.io/integrations/) Solutions ### Solutions * [Web / Full Stack Development](https://sentry.io/for/full-stack/) * [Mobile Crash Reporting](https://sentry.io/solutions/mobile-developers/) * [Game Crash Reporting](https://sentry.io/solutions/game-developers/) * [AI Observability](https://sentry.io/solutions/ai-observability/) * [Application Performance Monitoring](https://sentry.io/solutions/application-performance-monitoring/) * [Application Observability](https://sentry.io/solutions/application-observability/) * [Real User Monitoring](https://sentry.io/solutions/real-user-monitoring-rum/) * [Ecommerce](https://sentry.io/solutions/ecommerce/) * [Enterprise](https://sentry.io/for/enterprise/) * [Startups](https://sentry.io/for/startups/) * [All SDKs](https://sentry.io/platforms/) Resources Learn * [Blog](https://blog.sentry.io/) * [Changelog](https://sentry.io/changelog/) * [Sandbox](https://sandbox.sentry.io/) * [Resources](https://sentry.io/resources/) * [Syntax](https://syntax.fm/) * [Customers](https://sentry.io/customers/) * [Cookbook](https://sentry.io/cookbook/) Support * [Contact Us](https://sentry.io/contact/enterprise/) * [Help Center](https://help.sentry.io/) * [Status](https://status.sentry.io/) Hang out with us * [Sentry Build](https://sentry.io/resources/sentry-build/) * [Events](https://sentry.io/events/) * [Merch](https://sentry.shop/) [Docs](https://docs.sentry.io/) [Pricing](https://sentry.io/pricing/) [Sign In](https://sentry.io/auth/login/)[Get Demo](https://sentry.io/demo/)[Get Started](https://sentry.io/signup/) * Platform Products ### Products * [Error Monitoring](https://sentry.io/product/error-monitoring/) * [Logs](https://sentry.io/product/logs/) * [Session Replay](https://sentry.io/product/session-replay/) * [Metrics NEW](https://sentry.io/product/metrics/) * [Tracing](https://sentry.io/product/tracing/) * [Profiling](https://sentry.io/product/profiling/) * [Size Analysis](https://sentry.io/product/size-analysis/) * [Cron Monitoring](https://sentry.io/product/cron-monitoring/) * [Uptime Monitoring](https://sentry.io/product/uptime-monitoring/) ### Products * [Error Monitoring](https://sentry.io/product/error-monitoring/) * [Logs](https://sentry.io/product/logs/) * [Session Replay](https://sentry.io/product/session-replay/) * [Metrics NEW](https://sentry.io/product/metrics/) * [Tracing](https://sentry.io/product/tracing/) * [Profiling](https://sentry.io/product/profiling/) * [Size Analysis](https://sentry.io/product/size-analysis/) * [Cron Monitoring](https://sentry.io/product/cron-monitoring/) * [Uptime Monitoring](https://sentry.io/product/uptime-monitoring/) AI Debugging ### AI Debugging * [Seer NEW](https://sentry.io/product/seer/) * [Agent NEW](https://sentry.io/product/seer/agent/) * [Autofix NEW](https://sentry.io/product/seer/autofix/) * [AI Code Review NEW](https://sentry.io/product/seer/ai-code-review/) ### AI Debugging * [Seer NEW](https://sentry.io/product/seer/) * [Agent NEW](https://sentry.io/product/seer/agent/) * [Autofix NEW](https://sentry.io/product/seer/autofix/) * [AI Code Review NEW](https://sentry.io/product/seer/ai-code-review/) Integrations ### Integrations * [![Image 3](https://blog.sentry.io/astro-assets/nav-icons/github.png)Github](https://sentry.io/integrations/github/) * [![Image 4](https://blog.sentry.io/astro-assets/nav-icons/slack.png)Slack](https://sentry.io/integrations/slack/) * [Sentry CLI](https://cli.sentry.dev/) * [Sentry MCP](https://mcp.sentry.dev/) * [All Integrations](https://sentry.io/integrations/) ### Integrations * [![Image 5](https://blog.sentry.io/astro-assets/nav-icons/github.png)Github](https://sentry.io/integrations/github/) * [![Image 6](https://blog.sentry.io/astro-assets/nav-icons/slack.png)Slack](https://sentry.io/integrations/slack/) * [Sentry CLI](https://cli.sentry.dev/) * [Sentry MCP](https://mcp.sentry.dev/) * [All Integrations](https://sentry.io/integrations/) * Solutions * [Web / Full Stack Development](https://sentry.io/for/full-stack/) * [Mobile Crash Reporting](https://sentry.io/solutions/mobile-developers/) * [Game Crash Reporting](https://sentry.io/solutions/game-developers/) * [AI Observability](https://sentry.io/solutions/ai-observability/) * [Application Performance Monitoring](https://sentry.io/solutions/application-performance-monitoring/) * [Application Observability](https://sentry.io/solutions/application-observability/) * [Real User Monitoring](https://sentry.io/solutions/real-user-monitoring-rum/) * [Ecommerce](https://sentry.io/solutions/ecommerce/) * [Enterprise](https://sentry.io/for/enterprise/) * [Startups](https://sentry.io/for/startups/) * [All SDKs](https://sentry.io/platforms/) * Resources Learn ### Learn * [Blog](https://blog.sentry.io/) * [Changelog](https://sentry.io/changelog/) * [Sandbox](https://sandbox.sentry.io/) * [Resources](https://sentry.io/resources/) * [Syntax](https://syntax.fm/) * [Customers](https://sentry.io/customers/) * [Cookbook](https://sentry.io/cookbook/) ### Learn * [Blog](https://blog.sentry.io/) * [Changelog](https://sentry.io/changelog/) * [Sandbox](https://sandbox.sentry.io/) * [Resources](https://sentry.io/resources/) * [Syntax](https://syntax.fm/) * [Customers](https://sentry.io/customers/) * [Cookbook](https://sentry.io/cookbook/) Support ### Support * [Contact Us](https://sentry.io/contact/enterprise/) * [Help Center](https://help.sentry.io/) * [Status](https://status.sentry.io/) ### Support * [Contact Us](https://sentry.io/contact/enterprise/) * [Help Center](https://help.sentry.io/) * [Status](https://status.sentry.io/) Hang out with us ### Hang out with us * [Sentry Build](https://sentry.io/resources/sentry-build/) * [Events](https://sentry.io/events/) * [Merch](https://sentry.shop/) ### Hang out with us * [Sentry Build](https://sentry.io/resources/sentry-build/) * [Events](https://sentry.io/events/) * [Merch](https://sentry.shop/) ![Image 7: Bi-weekly Intro to Sentry Demo](https://blog.sentry.io/astro-assets/nav-icons/intro-demo.png) ### Bi-weekly Intro to Sentry Demo See Sentry in action and learn how errors, performance issues, and context fit together to help you find bugs faster and ship with confidence. Join us bi-weekly on Thursdays! [RSVP](https://sentry.io/resources/find-fix-test/) * [Docs](https://docs.sentry.io/) * [Pricing](https://sentry.io/pricing/) [Sign In](https://sentry.io/auth/login/)[Get Demo](https://sentry.io/demo/)[Get Started](https://sentry.io/signup/) [← Back to Blog Home](https://blog.sentry.io/) ![Image 8: Rahul Chhabria](https://blog.sentry.io/_vercel/image?url=_astro%2Frahul-chhabria.I3yTTzQR.jpg&w=640&q=100) [Rahul Chhabria](https://blog.sentry.io/authors/rahul-chhabria/)- April 28, 2026 ·9 min read ![Image 9: Introducing Seer Agent: The answer is already in Sentry. Now you can ask for it.](https://blog.sentry.io/_vercel/image?url=_astro%2Fintroducing-seer-agent-the-answer-is-already-in-sentry-now-you-can-ask-for-it.DRm_FyHB.jpg&w=1200&q=100) > **TL;DR** — We’re launching Seer Agent, which lets you ask questions and get answers based on everything Sentry knows about your app. Seer Agent is available in beta for all users today. Pop into Sentry, hit `Cmd + /` or at mention it in Slack to fix anything. Keep reading to see how cool it really is. This is a story about an engineer’s night that could have been bad, but ended up… not so bad. A few weeks ago, on a Saturday, our [AI debugger, Seer](https://sentry.io/product/seer/), started failing. ![Image 10: Sentry Slack alert showing a critical Seer error volume spike with 5,806 events in the last hour](https://blog.sentry.io/_vercel/image?url=_astro%2Fslack-error-spike.BCT8Fi5B.png&w=1200&q=100) Note the big scary spike on the right. The errors were generic failures from the LLM calls, nothing that pointed at a root cause. Most of the team wasn’t scheduled to be on this weekend, and it just so happened Indragie, our Head of AI, was online. He started paging engineers. While he waited for people to come online, he opened up a tool we’ve been testing internally for a few months now: Seer Agent. Indragie told Seer Agent a bit about what he was seeing, and asked it to figure out what was going on. It came back in seconds. The model calls were being rate-limited in specific regions for a specific model, even though we had enough provisioned throughput to handle the traffic. The rate limiting turned out to be a symptom of an upstream infrastructure outage on the provider’s side, which we confirmed after the incident, but Seer Agent had already pointed us at the exact region-and-model pattern that made the provider’s role obvious. Everything else was fine. ![Image 11: Seer Agent in the Sentry UI investigating elevated error rates and identifying GCP Vertex AI rate limiting on gemini-2.5-flash-lite across European regions](https://blog.sentry.io/_vercel/image?url=_astro%2Fseer-agent-investigation.CO2JTEGI.png&w=3840&q=100) That’s the kind of finding that would normally start with someone pulling up a dashboard, filtering by region, cross-referencing traffic against error rate, noticing the shape, and then working backwards to why one specific region was stumbling. Indragie knows his stuff, but he’s not contributing to the codebase day to day, he’s management ;), so it would have taken him at least half an hour to get there. If we’re being honest, probably longer. He had the root cause ready before the on-call engineer joined the channel. That’s the job Seer Agent is for: to investigate any issue in your application from ‘big super visible outage that has people shouting at you on Twitter’ to ‘things are running slow and you don’t know why’. **Today, we’re rolling out [Seer Agent](https://sentry.io/product/seer/agent/) to everyone in open beta.** ## [](https://blog.sentry.io/introducing-seer-agent/#the-problem-isnt-always-an-issue-0)The problem isn’t always an issue Seer’s original premise was simple: when Sentry catches an issue, Seer reads the stack trace, the trace data, the logs, replays, commit history, and the code, and tells you what’s wrong. It works well because the investigation has a concrete starting point (the issue), and the data you need is already linked to it. But a lot of debugging doesn’t start with an error. Sometimes it starts the way Indragie’s example started: you do have an issue, but the error message isn’t the most helpful and the real failure is somewhere upstream that the stack trace doesn’t reach. In all of those cases, you know something about the symptom. You just don’t know where to look. So you start manually: open the trace explorer, write a query, filter by environment, group by region, switch to [logs](https://sentry.io/product/logs/), pivot on a tag, go look at the service that’s upstream of this one, check its error rates, go back to traces, try a different span attribute. You’re not debugging yet. You’re navigating to where the debugging will happen. Seer Agent is the tool that does that navigation for you. You describe what you’re seeing, and it does the traversal across all of the context Sentry has on your system and tells you what it found. ![Video 1](https://blog.sentry.io/videos/posts/introducing-seer-agent-the-answer-is-already-in-sentry-now-you-can-ask-for-it/seer-agent.mp4) ## [](https://blog.sentry.io/introducing-seer-agent/#your-telemetry-is-already-a-graph-1)Your telemetry is already a graph You can already search across your telemetry in Sentry’s Explore product. You can write queries against traces, filter logs, pivot on attributes. Explore is powerful, and for people who already know the ins and outs of their Sentry data it’s the fastest way to answer a specific question. The problem with starting a debugging session in Explore is that you have to know the shape of your data before you can ask anything. If you don’t know which service is upstream of the failing one, you can’t filter for it. If you don’t know what span attribute to group by, the group-by is a shrug. Explore rewards operators who already have the map. Seer Agent doesn’t search your telemetry the way a generic LLM with a search tool would. Sentry’s telemetry is already [trace-connected](https://sentry.io/product/tracing/). When an error happens, we know the trace it happened in. It knows the spans inside that trace, the logs emitted during those spans, the deploy that was live at the time, and the commits in that deploy. The agent walks those connections directly. It isn’t guessing at time ranges and hoping the right rows show up in a text search; it’s traversing a graph that was built at ingest. Concretely: if you ask about an error, Seer Agent can pull the exact trace that produced it, the exact spans in that trace, the exact logs emitted by those spans, and the exact source lines the spans came from, without a single `WHERE timestamp BETWEEN` clause. Then it can walk the same graph in the other direction: which other services participated in traces that touched this endpoint, which of them were unhealthy at the same moment, and what their error rates looked like. That’s what made Indragie’s investigation fast. He didn’t tell Seer Agent “look at region-level error rates for the Vertex AI provider.” He gave it the Sentry issue. It pulled the trace, saw which regions the failing calls were routed to, cross-referenced against recent calls to other models that went through the same provider, noticed that one specific model family was failing in specific regions while others were fine, and surfaced the pattern. Four steps of manual pivoting, done in one pass. ## [](https://blog.sentry.io/introducing-seer-agent/#fixing-the-hard-issues-2)Fixing the hard issues Some bugs are fun to investigate and tackle yourself. “Lmao look at this silly line of code, who wrote this — oh no, it was me.” Others are not. They’re big and ugly and complex and require you to have (or quickly obtain) an absurd amount of context in your brain just to know where to start. Not coincidentally, these are things Seer Agent is very good at. **Failures whose root cause is upstream of your service.** Your stack trace ends at your own call site; the real cause is a 429 from someone else’s data center. Without Seer Agent you go find the provider’s status page, check whether the region you use is affected, and correlate against your own traffic. Seer Agent correlates the traffic against the request shape (provider, model, region, time) and tells you whether the failure is distributed in a pattern that indicates an upstream cause before you open another tab. **Failures that don’t trigger a clean alert.** A slow degradation on a single endpoint, a 1% error rate that started two hours ago, a tail-latency increase that’s only visible in p99. These are the investigations that start with “I noticed this and I want to know if it’s real.” Seer Agent can pull the baseline for you, compare the current window against it, and tell you whether the thing you noticed is statistically interesting or noise. **Failures that span services.** An issue fires in service A, but the real cause is that service B started returning malformed responses ten minutes ago. A trace-connected graph is the only way to see this cleanly, and a human walking the graph manually will lose context two hops in. The agent doesn’t. The bottleneck moves from “where do I look” to “what do I do about what I found,” which is where you actually want your engineers spending their time. ## [](https://blog.sentry.io/introducing-seer-agent/#multiplayer-mode-in-slack-3)Multiplayer Mode in Slack The Slack Seer agent is in active development, but in beta and ready to use today. You’ll be able to start an investigation the same way you’d ask an on-call engineer, by DMing or mentioning it in an incident channel, without having to bounce to the Sentry UI while you’re trying to put out a fire. Here’s an example how we were using Seer Agent in Slack while building it: ![Image 12: Slack thread showing Seer Agent investigating a user feedback report about Seer failing at the create PR step, with a detailed root cause analysis on GitHub App installation token 404s](https://blog.sentry.io/_vercel/image?url=_astro%2Fslack-multiplayer.C__9JSMp.png&w=1200&q=100) The more interesting thing is that the investigation becomes multiplayer. In the Sentry UI, Seer Agent is a solo tool. But in Slack, anyone in the channel can redirect it mid-step, add context the agent didn’t have, or just watch the traversal and learn the system a little better. The investigation also stays in the thread after the incident resolves, so when the same pattern shows up next month, someone can search for it instead of starting over. You can also trigger Autofix directly from Slack. Sentry alerts now include a “Fix with Seer” button and an initial read on the likely error. Clicking it kicks off the full Autofix workflow. This is currently in public beta. Read more about it in the [docs](https://docs.sentry.io/product/ai-in-sentry/seer/). ![Image 13: Slack notification for a ReferenceError in javascript-nextjs with a 'Fix with Seer' button and an initial guess about the root cause](https://blog.sentry.io/_vercel/image?url=_astro%2Fslack-fix-with-seer.DMJdN-wD.png&w=1200&q=100) The setup is light. If you already have the Sentry [Slack integration](https://docs.sentry.io/organization/integrations/notification-incidents/slack/) installed, the Fix with Seer button on your error alerts is already live. If you don’t, install it from Settings → Integrations. To DM Seer Agent or @mention it in a channel, run `/sentry link` in Slack to connect your account — if the Sentry app is already installed, just pick the same workspace when you link and the new features turn on. ## [](https://blog.sentry.io/introducing-seer-agent/#what-were-building-next-4)What we’re building next A few of the things on the short list, roughly ordered by when you’ll see them: **Auto-triage on incident creation.** Right now, you have to go to Sentry or Slack and prompt Seer. The better version is the one where an incident getting created automatically fires off an investigation and posts the findings back to the incident channel before anyone has to ask. There’s a design for this on our side, and we’re starting with our own incident workflow. **Proactive follow-ups.** When the agent finishes an analysis, it should suggest the next question, not wait for you to figure out what to ask next. “Do you want me to check whether this pattern exists in other services?” is a cheap prompt to generate and a large quality-of-life win for investigations that run long. **Message queueing and forceful interrupts.** Small items, but both high-frequency complaints: you can’t queue a follow-up while the agent is thinking, and sometimes you want to kill the current step and redirect without losing the session. Both are on the near-term list. ## [](https://blog.sentry.io/introducing-seer-agent/#how-to-try-it-5)How to try it Seer Agent is in open beta for all Sentry users. Open any page in Sentry, hit `Cmd + /` or click the “Ask Seer” button, and ask it something. ![Image 14: Sentry issue detail page with the 'Ask Seer' button highlighted in the top-right corner](https://blog.sentry.io/_vercel/image?url=_astro%2Fask-seer-button.CQ3CD_RP.png&w=3840&q=100) Peek a the docs [here](https://docs.sentry.io/product/ai-in-sentry/seer/#seer-agent), and we’ll run a workshop on it next month if you want to watch the team drive it live. If you find a case where it falls over, [tell us](https://github.com/getsentry/sentry/discussions/105737). Half of what’s on the “what we’re building” list above came from people using it and telling us exactly where the agent went wrong. Published April 28, 2026 ![Image 15: Sentry Sign Up CTA](https://blog.sentry.io/_vercel/image?url=_astro%2Fsignup-cta.yT5JbhvH.png&w=640&q=100) Code breaks, fix it faster Sign up for Sentry and monitor your application in minutes. [Try Sentry Free →](https://sentry.io/signup) Share [](https://twitter.com/intent/tweet?text=Introducing%20Seer%20Agent%3A%20The%20answer%20is%20already%20in%20Sentry.%20Now%20you%20can%20ask%20for%20it.&url=https%3A%2F%2Fblog.sentry.io%2Fintroducing-seer-agent%2F&via=sentry)[](https://bsky.app/intent/compose?text=Introducing%20Seer%20Agent%3A%20The%20answer%20is%20already%20in%20Sentry.%20Now%20you%20can%20ask%20for%20it.%20https%3A%2F%2Fblog.sentry.io%2Fintroducing-seer-agent%2F)[](https://news.ycombinator.com/submitlink?u=https%3A%2F%2Fblog.sentry.io%2Fintroducing-seer-agent%2F&t=Introducing%20Seer%20Agent%3A%20The%20answer%20is%20already%20in%20Sentry.%20Now%20you%20can%20ask%20for%20it.)[](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fblog.sentry.io%2Fintroducing-seer-agent%2F&title=Introducing%20Seer%20Agent%3A%20The%20answer%20is%20already%20in%20Sentry.%20Now%20you%20can%20ask%20for%20it.) Topics [Product Updates](https://blog.sentry.io/product-updates/) [![Image 16: New ways to agentically build and edit dashboards](https://blog.sentry.io/_vercel/image?url=_astro%2Fdashboard-updates.tJ4Gjqfa.jpg&w=640&q=100)](https://blog.sentry.io/dashboard-updates/) ### [New ways to agentically build and edit dashboards](https://blog.sentry.io/dashboard-updates/) Sentry dashboards just got a major upgrade: create dashboards with AI agents, manage them via the CLI, and clone pre-built templates for common monitoring use cases. [Read More](https://blog.sentry.io/dashboard-updates/)[![Image 17: Monitor Unreal Engine Game Performance with Application Metrics](https://blog.sentry.io/_vercel/image?url=_astro%2Funreal-engine-performance-metrics.CvNl8oky.jpeg&w=640&q=100)](https://blog.sentry.io/unreal-engine-performance-metrics/) ### [Monitor Unreal Engine Game Performance with Application Metrics](https://blog.sentry.io/unreal-engine-performance-metrics/) The Unreal SDK now auto-instruments FPS, frame time, network health, and game stats, giving your team real player performance data in production. [Read More](https://blog.sentry.io/unreal-engine-performance-metrics/)[![Image 18: Improved debugging for Expo apps with the React Native SDK](https://blog.sentry.io/_vercel/image?url=_astro%2Fdebugging-expo-react-native-sdk.B5ANgk1G.jpg&w=640&q=100)](https://blog.sentry.io/debugging-expo-react-native-sdk/) ### [Improved debugging for Expo apps with the React Native SDK](https://blog.sentry.io/debugging-expo-react-native-sdk/) Events from Expo apps account for about 75% of the total event volume we receive from React Native apps. That number made it an easy decision to invest in updates to the Sentry React Native SDK to improve the debugging and performance workflow for your Expo apps. [Read More](https://blog.sentry.io/debugging-expo-react-native-sdk/) [![Image 19: Syntax.fm logo](https://blog.sentry.io/syntax-logo.png)](https://syntax.fm/) ### Listen to the Syntax Podcast Of course we sponsor a developer podcast. Check it out on your favorite listening platform. [Listen To Syntax](https://syntax.fm/) ### Company * [About](https://sentry.io/about/) * [Blog](https://blog.sentry.io/) * [Careers](https://sentry.io/careers/) * [Contact Us](https://sentry.io/contact/enterprise/) * [Trust](https://sentry.io/trust/) ### Platform * [Error Monitoring](https://sentry.io/product/error-monitoring/) * [Logs](https://sentry.io/product/logs/) * [Seer](https://sentry.io/product/seer/) * [Session Replay](https://sentry.io/product/session-replay/) * [Metrics](https://sentry.io/product/metrics/) * [Tracing](https://sentry.io/product/tracing/) * [Uptime Monitoring](https://sentry.io/product/uptime-monitoring/) * [Profiling](https://sentry.io/product/profiling/) * [Cron Monitoring](https://sentry.io/product/cron-monitoring/) * [Integrations](https://sentry.io/integrations/) ### Solutions * [Web / Full Stack Development](https://sentry.io/for/full-stack/) * [Mobile Crash Reporting](https://sentry.io/solutions/mobile-developers/) * [Game Crash Reporting](https://sentry.io/solutions/game-developers/) * [AI Observability](https://sentry.io/solutions/ai-observability/) * [Application Performance Monitoring](https://sentry.io/solutions/application-performance-monitoring/) * [Application Observability](https://sentry.io/solutions/application-observability/) * [Real User Monitoring](https://sentry.io/solutions/real-user-monitoring-rum/) * [Ecommerce](https://sentry.io/solutions/ecommerce/) * [Enterprise](https://sentry.io/for/enterprise/) * [Startups](https://sentry.io/for/startups/) ### Get Help * [Docs](https://docs.sentry.io/) * [Help Center](https://help.sentry.io/) * [Status](https://status.sentry.io/) * [Dev Resources](https://develop.sentry.dev/getting-started/) [Terms](https://sentry.io/terms/)[Security & Compliance](https://sentry.io/security/)[Privacy](https://sentry.io/privacy/) [](https://sentry.io/)[](https://opensourcepledge.com/members/sentry/) [![Image 20](https://blog.sentry.io/astro-assets/nav-icons/x-twitter.png) Twitter Menu Button](https://x.com/sentry/)[![Image 21](https://blog.sentry.io/astro-assets/nav-icons/github.png) Github Social Menu Button](https://github.com/getsentry/)[![Image 22](https://blog.sentry.io/astro-assets/nav-icons/linkedin.png) LinkedIn Menu Button](https://www.linkedin.com/company/getsentry/)[![Image 23](https://blog.sentry.io/astro-assets/nav-icons/discord.png) Discord Menu Button](https://discord.gg/sentry) © 2026 • Sentry is a registered Trademark of Functional Software, Inc.