# sentry Published articles for sentry. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Debugging our AI search assistant with agent tracing DevFeed: [Debugging our AI search assistant with agent tracing]() Original publisher: [Read original article]() Author: Dominik Buszowiecki; Shaun Kaasten Published: 2026-09-11T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [AI search](), [agent observability](), [debugging](), [tracing](), [Large Language Model]() Tags: [agent](), [ai](), [api](), [debugging](), [errors](), [eval](), [llm](), [search](), [sentry](), [tracing]() ### AI overview Sentry engineers describe how they debugged the Search Query Assistant, which converts natural-language prompts into Sentry Syntax queries. They used evals for performance measurement and AI Conversation tracing to investigate failures, including a bug involving custom numerical attributes that caused queries to return no results. ### Source excerpt See how Sentry engineers used AI Conversations to debug a natural language search assistant and fix a tricky query generation bug. ## How we built an automated debugging workflow at Sentry DevFeed: [How we built an automated debugging workflow at Sentry]() Original publisher: [Read original article]() Author: Dhrumil Parekh Published: 2026-08-06T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [debugging](), [Automation](), [Artificial Intelligence](), [Claude](), [GitHub](), [Server]() Tags: [agent](), [ai](), [automated](), [automation](), [bugs](), [claude](), [debugging](), [github](), [pull-requests](), [review](), [sentry](), [slack](), [tool](), [workflow](), [workflows]() ### AI overview Sentry describes how it uses Seer, an AI-powered debugging agent, to detect issues, identify root causes, generate fixes, open GitHub pull requests, and route work for human review. The article also explains how organizations can control the level of automation. ### Source excerpt How Sentry uses Seer autofix and Claude routines to build an automated debugging workflow that detects, fixes, and routes code issues automatically. ## Sentry's Greg Pstrucha on why a better prompt won't fix your agent's code DevFeed: [Sentry's Greg Pstrucha on why a better prompt won't fix your agent's code]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T00:04:02Z Content type: opinion Language: en Sources: [WorkOS Blog]() Topics: [Artificial Intelligence](), [Tooling](), [coding](), [Software](), [Large Language Model]() Tags: [agent](), [agents](), [ai](), [ai-engineer](), [code](), [evals](), [metrics](), [quality](), [sentry](), [software](), [software-engineer](), [test](), [tests](), [tooling]() ### AI overview Sentry staff engineer Greg Pstrucha argues that improving AI-generated code requires more than better prompts. In his discussion of the "Stop Prompting" talk, he recommends linters, strong tests, type systems, frameworks, and skills as baseline safeguards, supplemented by evaluations for harder-to-codify quality judgments. ### Source excerpt Sentry staff engineer Greg Pstrucha on linters, stronger tests, evals for Seer, and the quality metrics agents game -- from AI Engineer World's Fair 2026. ## Connecting OpenTelemetry Traces with Sentry Errors in One Trace Waterfall DevFeed: [Connecting OpenTelemetry Traces with Sentry Errors in One Trace Waterfall]() Original publisher: [Read original article]() Author: Johannes Daxböck; Neel Shah Published: 2026-08-05T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [OpenTelemetry](), [tracing](), [telemetry](), [SDKs]() Tags: [errors](), [instrumentation](), [logs](), [opentelemetry](), [sdk](), [sdks](), [sentry](), [tracing]() ### AI overview Sentry's OtlpIntegration connects OpenTelemetry traces with Sentry errors and other events, allowing them to appear together in a trace waterfall. It reads the active OTel trace context and associates it with Sentry events while configuring an OTLP exporter for Sentry. ### Source excerpt The OtlpIntegration bridges OTel traces and Sentry errors. Keep your OTel setup, add Sentry for errors, and see both in one trace waterfall. ## Sentry Unreal Engine SDK Adds Session Replay to Crash Reports DevFeed: [Sentry Unreal Engine SDK Adds Session Replay to Crash Reports]() Original publisher: [Read original article]() Author: Ivan Tustanivskyi Published: 2026-07-24T09:00:00Z Content type: release Language: en Sources: [Sentry Blog]() Topics: [session replay](), [Unreal Engine](), [SDK](), [debugging](), [tracing]() Tags: [crash](), [debugging](), [sdk](), [sentry](), [session-replay](), [trace](), [unreal]() ### AI overview Sentry's Unreal Engine SDK adds Session Replay, recording the last several seconds of gameplay and attaching the footage to crash reports. Developers can review rendered frames alongside context, breadcrumbs, logs, and traces to investigate what led to a crash. ### Source excerpt 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. ## Logging Best Practices for Debugging Applications DevFeed: [Logging Best Practices for Debugging Applications]() Original publisher: [Read original article]() Author: Ben Coe Published: 2026-07-09T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [Logging](), [debugging](), [observability](), [audit](), [Instrumentation]() Tags: [audit](), [best-practices](), [debugging](), [how-to](), [instrumentation](), [learn](), [logging](), [observability](), [sentry]() ### AI overview This article presents practical logging best practices for applications. It recommends adding targeted log lines, using temporary instrumentation during investigations, recording runtime decisions and intermediate outcomes, and auditing access and mutating operations to make production software easier to debug and understand. ### Source excerpt Learn logging best practices: what to log, how to structure messages, and what to avoid. Practical tips with Sentry's structured logging. ## How the Usage app uses Sentry to detect crashes, silent errors, and build regressions DevFeed: [How the Usage app uses Sentry to detect crashes, silent errors, and build regressions]() Original publisher: [Read original article]() Author: Dan Mindru; Oleh Stasula Published: 2026-07-02T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [App](), [monitor](), [Processes](), [iphone](), [data]() Tags: [app](), [apple](), [dependency](), [errors](), [guest-post](), [iphone](), [mac](), [memory](), [monitor](), [network](), [process](), [sentry]() ### AI overview This guest post explains how the Usage system activity monitor uses Sentry to detect crashes, silent errors, build issues, and user feedback problems. The app runs across iPhone, iPad, and Mac and depends partly on undocumented APIs, so OS updates can change data structures without notice. Separate Sentry projects track the app's cooperating components and their failure modes. ### Source excerpt How the Usage app uses Sentry to catch crashes, silent errors, and build regressions before 1.6 million users notice. ## Catch visual regressions with Snapshots, now in beta DevFeed: [Catch visual regressions with Snapshots, now in beta]() Original publisher: [Read original article]() Author: Max Topolsky Published: 2026-06-11T09:00:00Z Content type: release Language: en Sources: [Sentry Blog]() Topics: [Testing](), [ci](), [Front end](), [User experience (UX)](), [Test coverage]() Tags: [agent](), [ci](), [frontend](), [sentry](), [testing](), [ux]() ### AI overview Sentry Snapshots is in beta and provides screenshot diffing in CI to detect unintended visual changes on each commit. The article explains snapshot testing, its use as a guardrail for agent-generated changes, and how Sentry used Snapshots to improve its own toolbar UX. ### Source excerpt 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. ## Errors, traces, logs, metrics: when to reach for what DevFeed: [Errors, traces, logs, metrics: when to reach for what]() Original publisher: [Read original article]() Author: Sergiy Dybskiy Published: 2026-06-05T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [SIEM, Security, Observability](), [telemetry](), [tracing](), [Logging](), [debugging]() Tags: [debugging](), [errors](), [logs](), [metrics](), [sentry](), [telemetry](), [traces]() ### AI overview This developer guide explains when to use errors, traces, logs, and metrics during application instrumentation and debugging. It distinguishes the question each telemetry signal answers and describes how the signals support different workflows. ### Source excerpt 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. ## You don't need to pick one: how Sentry and OpenTelemetry work together DevFeed: [You don't need to pick one: how Sentry and OpenTelemetry work together]() Original publisher: [Read original article]() Author: Lazar Nikolov Published: 2026-05-27T00:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [OpenTelemetry](), [telemetry](), [tracing](), [Traces](), [context](), [Instrumentation](), [React](), [SDKs]() Tags: [frontend](), [instrumentation](), [opentelemetry](), [sentry](), [telemetry](), [traces](), [tracing](), [w3c]() ### AI overview This article explains how to combine Sentry and OpenTelemetry in a web application. It recommends keeping OpenTelemetry for backend instrumentation, using the Sentry SDK on the frontend for browser context and application features, and exporting backend traces and logs to Sentry through OTLP directly or through an OpenTelemetry Collector. Sentry's OTLP ingest supports traces and logs, but not metrics at the time described. ### Source excerpt Use Sentry on the frontend, keep OpenTelemetry on the backend, and choose direct OTLP or Collector forwarding for OTLP events. ## Sentry MCP and CLI give coding agents production context for debugging DevFeed: [Sentry MCP and CLI give coding agents production context for debugging]() Original publisher: [Read original article]() Author: Sergiy Dybskiy Published: 2026-05-26T16:00:00Z Content type: opinion Language: en Sources: [Sentry Blog]() Topics: [AI-assisted coding](), [Model Context Protocol](), [debugging](), [Pull Request](), [Command-line interface](), [Testing]() Tags: [cli](), [coding-agents](), [debugging](), [mcp](), [review](), [root-cause-analysis](), [sentry](), [testing]() ### AI overview Coding agents often lack the production context needed to diagnose real-world bugs. This article explains how Sentry MCP and the Sentry CLI provide evidence such as stack traces, request payloads, environments, and breadcrumbs, enabling agents to investigate issues and open draft pull requests while humans remain involved. ### Source excerpt 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. ## Using Sentry Telemetry for Product Analytics DevFeed: [Using Sentry Telemetry for Product Analytics]() Original publisher: [Read original article]() Author: Rahul Chhabria Published: 2026-05-21T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [product analytics](), [telemetry](), [Traces](), [SIEM, Security, Observability]() Tags: [logs](), [metrics](), [product-analytics](), [sentry](), [telemetry](), [traces]() ### AI overview The article explains how developers can use Sentry traces, structured logs, and application metrics to answer product analytics questions such as onboarding completion, checkout latency, and signup changes. It emphasizes that telemetry can connect product findings to operational context and the code responsible. ### Source excerpt Your Sentry traces, logs, and metrics already answer most product analytics questions. Learn how to query existing telemetry for product insights. ## Sentry adds AI-agent and CLI tools for creating and editing dashboards DevFeed: [Sentry adds AI-agent and CLI tools for creating and editing dashboards]() Original publisher: [Read original article]() Author: Ben Coe; Steve Zegalia Published: 2026-05-14T09:00:00Z Content type: release Language: en Sources: [Sentry Blog]() Topics: [dashboards](), [Artificial Intelligence](), [Command-line interface](), [Monitoring]() Tags: [agents](), [ai](), [cli](), [dashboards](), [monitoring](), [sentry]() ### AI overview Sentry introduces AI-assisted dashboard creation and editing, CLI-based dashboard management, and customizable dashboard templates. The features support creating dashboards for monitoring needs and are described as available through Sentry's AI-powered capabilities and CLI. ### Source excerpt Create and edit Sentry dashboards with AI agents, the Sentry CLI, or pre-built templates you can clone and customize for your monitoring needs. ## Sentry + Encore DevFeed: [Sentry + Encore]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-04-29T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [error tracking](), [Back end](), [SDKs](), [Secrets Management]() Tags: [backend](), [error-tracking](), [sdk](), [secrets-management](), [sentry](), [tutorial]() ### AI overview A tutorial showing how to integrate Sentry error tracking into an Encore.ts backend. It covers installing and initializing the SDK, using a reusable error-handling wrapper, adding breadcrumbs, and verifying captured errors with a test endpoint. ### Source excerpt Error tracking for your backend services ## Ловим баги на клиенте: как мы написали свою систему для сбора клиентских ошибок DevFeed: [Ловим баги на клиенте: как мы написали свою систему для сбора клиентских ошибок]() Original publisher: [Read original article]() Author: Unclead (Badoo) Published: 2020-10-08T13:23:03Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [error tracking](), [App](), [Android](), [iOS]() Tags: [android](), [app](), [badoo](), [error-reporting](), [error-tracking](), [ios](), [sentry](), [tag-9e6194bca65c](), [tag-d96e238f1419]() ### AI overview This article explains how Badoo developed Gelato, an in-house system for collecting client-side errors across web, Android, and iOS applications. It discusses why the company built its own error-tracking system, how error data supports production monitoring and release analysis, and considerations for designing such a system. ### Source excerpt У нас в Badoo довольно много клиентских приложений. Помимо основных продуктов Badoo и Bumble, у которых есть как веб-версии (десктопная и мобильная), так и клиенты под нативные платформы (Android и iOS), ещё есть с десяток внутренних инструментов со своими UI. Для сбора клиентских ошибок мы используем собственную разработку под кодовым названием Gelatо. Последние два года я работал над её серверной частью и за это время открыл для себя много нового из мира разработки Error Tracking систем. Поэтому, если вам интересно узнать, что из себя представляет разработка системы сбора клиентских ошибок и о чём стоит подумать, если вы решите разрабатывать собственную, добро пожаловать под кат. Читать далее ## Undetected NDK crashes during a Firefox Focus Android release DevFeed: [Undetected NDK crashes during a Firefox Focus Android release]() Original publisher: [Read original article]() Published: 2020-10-05T18:08:05Z Content type: opinion Language: en Sources: [Colin The Shots]() Topics: [Firefox](), [Android](), [Google Play](), [Google](), [browser](), [releases](), [bug](), [dashboards]() Tags: [android](), [c-plus-plus](), [chrome](), [code](), [crash-reporting](), [crashes](), [dashboards](), [firefox](), [google-play](), [releases](), [reporting](), [sentry](), [uncategorized]() ### AI overview A Mozilla engineer recounts how Firefox Focus 8.0.4 for Android developed previously undetected NDK crashes during its Christmas 2018 production rollout. Sentry and Socorro missed crashes occurring inside Chrome WebViews, while Google Play Console exposed them as the rollout expanded. ### Source excerpt I loved working at Mozilla for the almost two years that I spent there. But even a great job has hard days. The weeks around Christmas of 2018 were a stressful nightmare. I'd been working as the ## Debugging Netlify Function Errors with Sentry DevFeed: [Debugging Netlify Function Errors with Sentry]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2019-01-31T19:30:00Z Content type: tutorial Language: en Sources: [HTTP Toolkit]() Topics: [Netlify](), [debugging](), [Serverless](), [Logging](), [AWS Lambda](), [Code]() Tags: [aws-lambda](), [debugging](), [error-reporting](), [errors](), [javascript](), [logging](), [netlify](), [sentry](), [serverless]() ### AI overview A tutorial on adding Sentry error reporting to Netlify Functions. It explains why serverless function errors can be difficult to detect and debug, then covers setup, DSN configuration, initialization, and handling errors that Netlify or AWS Lambda may otherwise swallow, delay, or lose. ### Source excerpt Netlify functions are a quick, easy & powerful tool, but like most serverless platforms, they can be even more difficult to debug & monitor than traditional server applications. It's a hard environment to precisely recreate locally, there's no machine you can SSH into in a pinch, and no built-in error notifications. Your code is going to break eventually, and you need the tools to fix it. HTTP Toolkit uses Netlify functions under the hood to manage user account information and Paddle checkout callbacks. If we hit errors here, people's payments will fail, or they'll stop being given access to paid features, so this can be pretty bad! I need to be able to catch errors immediately, debug and work out why they're happening, and confirm that my fixes work. Debugging & fixing issues here is a big topic, but one of the first steps is knowing exactly when & how errors happen. There's a few tools for this, but personally I've had a lot of success on projects recently with Sentry. They've got a generous free plan (5k errors a month), built-in integrations for almost everything, and some good & detailed error reporting tools too. If you can get Sentry set up, you'll get emails every time there's an error in your function, and you can explore the errors themselves in detail to work out exactly what failed. Perfect, but the setup for Netlify functions has a few extra steps. Start reporting errors to Sentry I'm going to be using JS here, and I'm assuming you've already got a working Netlify function set up. To add Sentry reporting from there, you need to: Create a Sentry account Create a Sentry project in that account for your functions Take the DSN for your Sentry project and set it as a SENTRY_DSN variable in your Netlify build npm install --save @sentry/node (the examples here require ^4.6.0) Initialize your error logging logic: const Sentry = require('@sentry/node'); const { SENTRY_DSN } = process.env; let sentryInitialized = false; export function initSentry() { if (SENTRY_D