Filtering 3rd parties out of Sentry

.env.sample

@@ -14,6 +14,7 @@ VITE_LEGACY_TRADE_BY_SOURCE_RANGE=
 SENTRY_ORG=
 SENTRY_PROJECT=
 SENTRY_AUTH_TOKEN=
+VITE_SENTRY_APPLICATION_KEY=
 
 # E2E
 CI=false

src/init-sentry.ts

@@ -8,6 +8,13 @@ if (config.sentryDSN) {
     integrations: [
       Sentry.tanstackRouterBrowserTracingIntegration(router),
       Sentry.captureConsoleIntegration({ levels: ['error'] }),
+      Sentry.thirdPartyErrorFilterIntegration({
+        filterKeys: [
+          import.meta.env.VITE_SENTRY_APPLICATION_KEY ||
+            'custom_application_key_carbon_app',
+        ],
+        behaviour: 'drop-error-if-contains-third-party-frames',
+      }),
     ],
     // Performance Monitoring
     tracesSampleRate: 1.0, // Capture 100% of the transactions, reduce in production!

src/vite-env.d.ts

@@ -9,6 +9,7 @@ interface ImportMetaEnv {
   readonly VITE_TENDERLY_ACCESS_KEY: string;
   readonly SENTRY_ORG: string;
   readonly SENTRY_PROJECT: string;
+  readonly VITE_SENTRY_APPLICATION_KEY: string;
   readonly SENTRY_AUTH_TOKEN: string;
 }
 

vite.config.ts

@@ -29,6 +29,9 @@ export default defineConfig(({ mode }) => {
       sentryVitePlugin({
         org: env.SENTRY_ORG,
         project: env.SENTRY_PROJECT,
+        applicationKey:
+          env.VITE_SENTRY_APPLICATION_KEY ||
+          'custom_application_key_carbon_app',
 
         // Auth tokens can be obtained from https://sentry.io/settings/account/api/auth-tokens/
         // and need `project:releases` and `org:read` scopes