void-instrumentation-setup

Create an instrumentation.ts file at the project root that dynamically imports instrumentation-node.ts or instrumentation-edge.ts based on NEXT_RUNTIME. Initialize Sentry in each runtime file with environment-based tracesSampleRate, and add a separate 'use client' SentryProvider for browser errors.

Initialize the OpenTelemetry NodeSDK inside instrumentation-node.ts only, using getNodeAutoInstrumentations and an OTLPTraceExporter pointed at your OTEL_EXPORTER_OTLP_ENDPOINT. Do not add OTel to the Edge runtime, since it cannot load Node native bindings and fails silently.

No, server instrumentation.ts does not cover the browser. Add a separate client-side SentryProvider component with 'use client' that calls Sentry.init once using the NEXT_PUBLIC_SENTRY_DSN environment variable, then wire it into app/layout.tsx.

The Edge runtime cannot load Node native modules, write to the filesystem, or use Node Buffer outside polyfills, so OTel auto-instrumentation silently fails. Keep Edge instrumentation minimal with only Sentry init and captureMessage or addBreadcrumb calls.

Use the beforeSend hook in Sentry.init to hash or strip user.id, email, and other identifiers before events are sent. Never log raw PII, and validate that user IDs appear hashed when inspecting events in the Sentry dashboard.