Dogfood sentry-webpack-plugin

[smeubank]

Background

With the sentry-unplugin work we will be able to monitor it in Sentry. This allows us to check the performance and tracing of our own product.

sentry-unplugin Sentry project

Outcomes:

• able to track quantity of usage
• this we will then be able to compare with sentry-unplugin data to determine which JS bundlers are being used the most
• able to detect any performance issues
• able to trace the different services (projects) involved with upload of source maps

Requirements:

• a new project in Sentry org
• Bare minimum transactions to be sent to that project
• should be a tag for bundler:"bundler-name"
  • obviously on sentry-webpack-plugin this should always be the webpack, but would be nice to have some check if possible
• we should be able to differentiate between CI or test stage transaction and what is sent from production environment
• strip down what is sent to Sentry to a bare minimum to reduce all risk of any PII sent Sentry

[smeubank]

@lforst did we decide to not do this? I cannot remember 😓

[lforst]

Ah right thanks for reminding me. I think we still wanted to do this - putting in progress.

[lforst]

Priorities are somewhere else and we are soon publishing from https://github.com/getsentry/sentry-javascript-bundler-plugins which has telemetry already