remove-sentry
Remove Sentry error tracking from both the frontend and Strapi while keeping structured logging in place. Only the error-reporting backend goes — your logging keeps working.
Use it when
- You don't use Sentry and want it and its configuration removed cleanly.
What it helps solve
- Removes an unused Sentry account dependency.
- Simplifies error-tracking setup when the project uses another tool or none.
- Keeps regular application logging in place.
What it removes
- UI: the
@sentry/nextjsdependency and the telemetry provider inapps/ui/src/lib/telemetry/providers/sentry.ts. Also its shareddataCollectionbaseline (sentry-data-collection.ts), the browser init inapps/ui/src/instrumentation-client.ts, theonRequestErrorhook ininstrumentation.ts, and thewithSentryConfigwrapper (imported from@sentry/nextjs/config) innext.config.mjs. Error boundaries switch fromSentry.captureExceptiontoconsole.error. - Strapi:
@strapi/plugin-sentryand its plugin config. - Docs and environment examples that mention Sentry.
Use remove-azure-monitor separately if Azure telemetry should also go.