{"id":49786,"date":"2025-06-23T05:13:41","date_gmt":"2025-06-23T05:13:41","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=49786"},"modified":"2025-06-23T05:17:47","modified_gmt":"2025-06-23T05:17:47","slug":"sentry-how-sentry-captures-errors-internally","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/sentry-how-sentry-captures-errors-internally\/","title":{"rendered":"Sentry: How Sentry Captures Errors Internally"},"content":{"rendered":"\n

Behind the Scenes: How Sentry Works at Runtime Level<\/p>\n\n\n\n

Sentry SDK sits inside your application, listens for errors at runtime, and sends them to the Sentry cloud<\/strong>, where you can view, debug, and track them in the dashboard.<\/strong><\/p>\n\n\n\n

\n\n\n\n

Complete Beginner-to-Intermediate Guide to How Sentry Captures Errors Internally<\/strong><\/h1>\n\n\n\n
\n

Learn how Sentry really works<\/strong> \u2014 how it collects errors, what it captures by default, how it integrates with your app runtime, and how it differs from traditional log readers.<\/p>\n<\/blockquote>\n\n\n\n

\n\n\n\n

\ud83e\udded What is Sentry?<\/h2>\n\n\n\n

Sentry<\/strong> is a powerful real-time error tracking and performance monitoring tool<\/strong> used by developers and DevOps teams to:<\/p>\n\n\n\n

    \n
  • Capture runtime errors and exceptions from applications<\/li>\n\n\n\n
  • Monitor performance issues (slow transactions, bottlenecks)<\/li>\n\n\n\n
  • Debug problems faster with detailed context (stack trace, user, request, etc.)<\/li>\n<\/ul>\n\n\n\n

    It supports 40+ programming languages and frameworks<\/strong> like Node.js, Python, PHP, Java, .NET, React, Flutter, and more.<\/p>\n\n\n\n

    Here’s the full flow in simple terms:<\/h3>\n\n\n\n
      \n
    1. You install and initialize the Sentry SDK<\/strong> in your app (e.g., Node, Laravel, Python, Flutter, etc.)<\/li>\n\n\n\n
    2. When your app throws an error or exception<\/strong>:\n
        \n
      • Sentry captures it automatically<\/strong> from the language runtime<\/li>\n\n\n\n
      • OR you can capture it manually<\/strong> using Sentry.captureException()<\/code><\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Sentry SDK collects contextual information<\/strong>:\n
          \n
        • Stack trace<\/li>\n\n\n\n
        • Request info (URL, headers, etc.)<\/li>\n\n\n\n
        • User info (if added)<\/li>\n\n\n\n
        • Environment (browser, OS, app version)<\/li>\n\n\n\n
        • Recent events (breadcrumbs)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • The SDK sends that data as a JSON payload via HTTPS<\/strong> to your Sentry project (Sentry Cloud or self-hosted server)<\/li>\n\n\n\n
        • You log into the Sentry Dashboard<\/strong> and:\n
            \n
          • View errors grouped by issue<\/li>\n\n\n\n
          • See full trace & context<\/li>\n\n\n\n
          • Track how often they happen<\/li>\n\n\n\n
          • Get alerts via Slack\/email<\/li>\n\n\n\n
          • Fix and mark issues as resolved<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
            \n\n\n\n

            \ud83d\udd0c How Does Sentry Work?<\/h2>\n\n\n\n

            \u274c Misconception:<\/h3>\n\n\n\n
            \n

            “Sentry reads from log files, right?”<\/p>\n<\/blockquote>\n\n\n\n

            \u2705 Truth:<\/h3>\n\n\n\n
            \n

            Sentry does NOT read logs from files.<\/strong>
            It works by embedding a lightweight SDK (software library)<\/strong> directly inside your application code.<\/p>\n<\/blockquote>\n\n\n\n

            \n\n\n\n

            \u2705 How Sentry Collects Errors Internally<\/h2>\n\n\n\n

            \u2705 Step-by-Step Breakdown:<\/h3>\n\n\n\n
              \n
            1. You install the Sentry SDK<\/strong> into your application.<\/li>\n\n\n\n
            2. You initialize the SDK<\/strong> with a DSN (Data Source Name).<\/li>\n\n\n\n
            3. The SDK hooks into the runtime environment<\/strong> (not the app server).<\/li>\n\n\n\n
            4. It automatically listens to:\n
                \n
              • Uncaught exceptions<\/li>\n\n\n\n
              • Unhandled promise rejections<\/li>\n\n\n\n
              • Warnings<\/li>\n\n\n\n
              • Framework-specific errors<\/li>\n<\/ul>\n<\/li>\n\n\n\n
              • Errors are immediately serialized into JSON and sent to Sentry<\/strong> via HTTPS.<\/li>\n\n\n\n
              • You see the data inside the Sentry web dashboard<\/strong> in real-time.<\/li>\n<\/ol>\n\n\n\n
                \n\n\n\n

                \ud83e\udde0 What Does Sentry Capture Automatically<\/em>?<\/h2>\n\n\n\n
                Feature<\/th>Captured by Default<\/th><\/tr><\/thead>
                Uncaught Exceptions<\/td>\u2705 Yes<\/td><\/tr>
                Unhandled Promise Errors<\/td>\u2705 Yes<\/td><\/tr>
                Stack Trace<\/td>\u2705 Yes<\/td><\/tr>
                HTTP Request Context<\/td>\u2705 Yes<\/td><\/tr>
                Environment Info (OS, Browser)<\/td>\u2705 Yes<\/td><\/tr>
                Breadcrumbs (User actions, logs)<\/td>\u2705 Yes<\/td><\/tr>
                User Agent<\/td>\u2705 Yes<\/td><\/tr>
                Performance Traces (if enabled)<\/td>\u2705 Yes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                \n\n\n\n

                \ud83d\udee0\ufe0f What You Can Add Manually<\/h2>\n\n\n\n
                Manual Method<\/th>Use Case<\/th><\/tr><\/thead>
                Sentry.captureException(err)<\/code><\/td>To capture handled errors<\/td><\/tr>
                Sentry.captureMessage(\"info\")<\/code><\/td>To log messages without errors<\/td><\/tr>
                Sentry.setUser({id, email})<\/code><\/td>To attach user context<\/td><\/tr>
                Sentry.setTag(\"env\", \"prod\")<\/code><\/td>To add custom tags<\/td><\/tr>
                Sentry.setContext(\"cart\", {...})<\/code><\/td>To pass structured metadata<\/td><\/tr>
                Sentry.addBreadcrumb({...})<\/code><\/td>To log custom breadcrumbs<\/td><\/tr>
                Sentry.startTransaction()<\/code><\/td>To start a manual performance trace<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                \n\n\n\n

                \ud83d\udd2c How Sentry Hooks into Runtime Environments<\/h2>\n\n\n\n
                Language \/ Stack<\/th>How It Hooks<\/th><\/tr><\/thead>
                Node.js<\/strong><\/td>process.on('uncaughtException')<\/code>, middleware, monkey patching http<\/code>, express<\/code>, etc.<\/td><\/tr>
                Python<\/strong><\/td>sys.excepthook<\/code>, threading<\/code>, logging<\/code>, Flask\/Django signal wrapping<\/td><\/tr>
                PHP<\/strong><\/td>register_shutdown_function()<\/code>, set_exception_handler()<\/code><\/td><\/tr>
                Java<\/strong><\/td>Thread.UncaughtExceptionHandler<\/code>, servlet filters, AOP<\/td><\/tr>
                Flutter\/Dart<\/strong><\/td>FlutterError.onError<\/code>, runZonedGuarded()<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

                These hooks let Sentry capture exceptions at the lowest level<\/strong> before they’re written to logs.<\/p>\n\n\n\n

                \n\n\n\n

                \ud83e\udd1d Can Sentry Integrate with Logging Frameworks?<\/h2>\n\n\n\n

                Yes. You can integrate it with your logging stack like:<\/p>\n\n\n\n

                  \n
                • winston<\/code> (Node.js)<\/li>\n\n\n\n
                • monolog<\/code> (Laravel, PHP)<\/li>\n\n\n\n
                • logback<\/code> \/ slf4j<\/code> (Java)<\/li>\n\n\n\n
                • Python’s built-in logging<\/code><\/li>\n<\/ul>\n\n\n\n

                  Example: Node.js + Winston<\/h3>\n\n\n
                  const<\/span> winston = require<\/span>('winston'<\/span>);\nconst<\/span> Sentry = require<\/span>('@sentry\/node'<\/span>);\nconst<\/span> SentryTransport = require<\/span>('@sentry\/winston'<\/span>).default<\/span>;\n\nSentry.init({ dsn: 'https:\/\/your-dsn@sentry.io\/projectId'<\/span> });\n\nconst<\/span> logger = winston.createLogger({\n  transports: [\n    new<\/span> winston.transports.Console(),\n    new<\/span> SentryTransport({ level: 'error'<\/span> }), \/\/ sends to Sentry<\/span>\n  ],\n});\n\nlogger.error('Database connection failed!'<\/span>);\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  \n\n\n\n
                  \ud83d\udd10 Is Sentry Safe to Use?<\/h2>\n\n\n\n
                  Yes. But:<\/p>\n\n\n\n
                    \n
                  • Avoid sending sensitive data (PII, passwords)<\/li>\n\n\n\n
                  • Use Sentry’s data scrubbing<\/strong> features<\/li>\n\n\n\n
                  • Use self-hosted Sentry<\/strong> if compliance is critical (e.g., GDPR, HIPAA)<\/li>\n<\/ul>\n\n\n\n
                    \n\n\n\n
                    \ud83d\udcca Where Sentry Runs in the Stack<\/h2>\n\n\n\n
                    Layer<\/th>Used by Sentry?<\/th><\/tr><\/thead>
                    OS \/ Kernel<\/td>\u274c No<\/td><\/tr>
                    Application Server<\/td>\u274c No<\/td><\/tr>
                    Language Runtime<\/strong><\/td>\u2705 YES<\/td><\/tr>
                    Application Code<\/strong><\/td>\u2705 YES (SDK)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                    So Sentry works inside your app process<\/strong>, not outside it.<\/p>\n\n\n\n
                    \n\n\n\n
                    \ud83c\udf93 Recap \u2014 How Sentry Works (Simple Flow)<\/h2>\n\n\n
                    Your App Code\n     \u2193\nSentry SDK hooks into language runtime\n     \u2193\nError<\/span> occurs (auto or manual capture)\n     \u2193\nError<\/span> serialized into JSON<\/span>\n     \u2193\nSent via HTTPS to sentry.io (or on-prem server)\n     \u2193\nVisible in<\/span> real-time on dashboard\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    \n\n\n\n
                    <\/h2>\n","protected":false},"excerpt":{"rendered":"
                    Behind the Scenes: How Sentry Works at Runtime Level Sentry SDK sits inside your application, listens for errors at runtime, and sends them to the Sentry cloud, where you can… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-49786","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49786","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=49786"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49786\/revisions"}],"predecessor-version":[{"id":49789,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/49786\/revisions\/49789"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=49786"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=49786"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=49786"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}