--- title: A practical guide to React error monitoring | daily.dev description: A guide to implementing React error monitoring across three levels: render-level (error boundaries and try-catch), business-level (silent logical errors via... canonical: https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: A practical guide to React error monitoring | daily.dev og:description: A guide to implementing React error monitoring across three levels: render-level (error boundaries and try-catch), business-level (silent logical errors via... og:url: https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb og:image: https://api.daily.dev/og/posts/QmxIyODzB.png og:image:alt: A practical guide to React error monitoring og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # A practical guide to React error monitoring **[Datadog](https://daily.dev/sources/datadog)** · 9 min read · 4 upvotes · 0 comments ## Summary A guide to implementing React error monitoring across three levels: render-level (error boundaries and try-catch), business-level (silent logical errors via validation), and global-level (root node callbacks introduced in React v19). Covers enriching errors with user, session, and application context including identifiers, browser data, and geographic info. Also addresses sanitizing error messages to prevent PII leaks and CWE-1295 vulnerabilities. The post concludes by showing how Datadog Error Tracking automates collection, enrichment, grouping, and AI-assisted investigation of React errors from both browser and React Native apps. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are the three root-node error callbacks introduced in React 19? React 19 introduced three callbacks at the root node for global error logging: onRecoverableError for errors React automatically recovered from, onCaughtError for errors captured within error boundaries, and onUncaughtError for errors not captured within error boundaries. These callbacks are passed as parameters to createRoot, giving visibility into errors that individual component-level error boundaries might miss. _Developers rolling out React 19 error handling can track version-specific API changes like this on daily.dev._ ### Why can't React error boundaries catch errors from event handlers or async code? Error boundaries only catch errors thrown during synchronous, client-side rendering, so they miss errors from event handlers, asynchronous code, or server-side rendering. For those cases, explicit error handling such as try-catch blocks around potentially problematic code is needed. Error boundaries also must be class components, though libraries like react-error-boundary provide hooks for functional components. _Teams debugging gaps in React error coverage can follow ongoing frontend reliability discussions on daily.dev._ ### What is CWE-1295 and why does it matter for logging error messages? CWE-1295 identifies the exposure of sensitive information in error messages as a common security weakness attackers can exploit to access user data or learn about system architecture, including filepaths, memory addresses, and usernames. Risks arise from patterns like template literals embedding user emails or URLs containing session tokens and API keys, so PII should be scrubbed before storing error logs and access to logs should be restricted. _Developers hardening error logging against data leaks can track security practices like this on daily.dev._ ## Similar posts on daily.dev - [Error Recovery Patterns: Building Resilient DeepSeek-R1 Applications](https://daily.dev/posts/error-recovery-patterns-building-resilient-deepseek-r1-applications-xvb4coeh6) · SitePoint · 0 upvotes · 0 comments - [Signal-Driven Error Monitoring: Detecting and Debugging Reactive Failures in Angular](https://daily.dev/posts/signal-driven-error-monitoring-detecting-and-debugging-reactive-failures-in-angular-r0d0mo3v3) · AppSignal · 1 upvotes · 0 comments - [Making the Browser Agent Resilient: Implementing Autonomous Error Handling and Retries](https://daily.dev/posts/making-the-browser-agent-resilient-implementing-autonomous-error-handling-and-retries-jyyalsbdl) · ITNEXT · 1 upvotes · 1 comments - [A Guide to Web Application Monitoring](https://daily.dev/posts/a-guide-to-web-application-monitoring-aowmrvcdn) · RUBYLAND · 0 upvotes · 0 comments - [React and React Native](https://daily.dev/posts/react-and-react-native-mwqbx4li7) · We Are .NET · 1 upvotes · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#react](https://daily.dev/tags/react), [#devops](https://daily.dev/tags/devops) [View this post on daily.dev](https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"A practical guide to React error monitoring","url":"https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb"},"datePublished":"2026-07-30T15:01:05.131Z","dateModified":"2026-09-14T08:30:52.087Z","description":"A guide to implementing React error monitoring across three levels: render-level (error boundaries and try-catch), business-level (silent logical errors via...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/347b277a3c0b27f78bbeb0ee5427e9a6?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/347b277a3c0b27f78bbeb0ee5427e9a6?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Datadog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Datadog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/8f9d7e3e4bd64bd7b9db9b2ea83e0c6a","url":"https://daily.dev/sources/datadog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"javascript,react,devops","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Datadog","item":"https://daily.dev/sources/datadog"},{"@type":"ListItem","position":3,"name":"A practical guide to React error monitoring"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/a-practical-guide-to-react-error-monitoring-qmxiyodzb#faq","mainEntity":[{"@type":"Question","name":"What are the three root-node error callbacks introduced in React 19?","acceptedAnswer":{"@type":"Answer","text":"React 19 introduced three callbacks at the root node for global error logging: onRecoverableError for errors React automatically recovered from, onCaughtError for errors captured within error boundaries, and onUncaughtError for errors not captured within error boundaries. These callbacks are passed as parameters to createRoot, giving visibility into errors that individual component-level error boundaries might miss. Developers rolling out React 19 error handling can track version-specific API changes like this on daily.dev."}},{"@type":"Question","name":"Why can't React error boundaries catch errors from event handlers or async code?","acceptedAnswer":{"@type":"Answer","text":"Error boundaries only catch errors thrown during synchronous, client-side rendering, so they miss errors from event handlers, asynchronous code, or server-side rendering. For those cases, explicit error handling such as try-catch blocks around potentially problematic code is needed. Error boundaries also must be class components, though libraries like react-error-boundary provide hooks for functional components. Teams debugging gaps in React error coverage can follow ongoing frontend reliability discussions on daily.dev."}},{"@type":"Question","name":"What is CWE-1295 and why does it matter for logging error messages?","acceptedAnswer":{"@type":"Answer","text":"CWE-1295 identifies the exposure of sensitive information in error messages as a common security weakness attackers can exploit to access user data or learn about system architecture, including filepaths, memory addresses, and usernames. Risks arise from patterns like template literals embedding user emails or URLs containing session tokens and API keys, so PII should be scrubbed before storing error logs and access to logs should be restricted. Developers hardening error logging against data leaks can track security practices like this on daily.dev."}}]} ```