error-tracking

To prevent PII from leaking into error tracking pipelines, route all exception reporting through a centralized wrapper that enforces a sanitizePII pass on every outbound payload, including breadcrumbs and extra context, before any external send occurs.

To capture exceptions across React component boundaries and route fallbacks, implement a layered coverage strategy where each error surface calls a centralized reporting wrapper, ensuring events reliably reach the tracker rather than only logging locally.

Environment gating does work for error reporting in non-production by routing exception capture to a local logger in development environments and sending events to the actual tracker only in production-equivalent environments.

The best way to centralize exception reporting without importing tracker SDKs directly is to expose a small set of wrapper functions like reportError, reportMessage, and addBreadcrumb that app code calls instead of the underlying SDK.

Exception reports silently fail to reach the tracker when error surfaces log locally but bypass the centralized wrapper, so auditing each layer to verify it calls the wrapper ensures the tracker actually receives events.