Unify console instrumentation to a single integration

[AbhiPrasad]

Description

Our console instrumentation is spread across different sdks and integrations, making for a confusing set up experience. We should try to unify this to be a single integration in the next major version of the SDK. This also allows us to look at enabling sending logs by default via console logs if enableLogs is set to true.

Our ideal end state is a single console integration that captures breadcrumbs by default, captures logs if enableLogs is set to true, and optionally captures errors if configured by users. This allows us to delete captureConsoleIntegration, and simplify breadcrumbsIntegration in browser (something we've wanted to do for a long time).

• @sentry/core - consoleIntegraiton (captures console as breadcrumbs): https://github.com/getsentry/sentry-javascript/blob/develop/packages/core/src/instrument/console.ts
• @sentry/core - consoleLoggingIntegration (captures console as logs): https://github.com/getsentry/sentry-javascript/blob/develop/packages/core/src/logs/console-integration.ts
• @sentry/core - captureConsoleIntegration (captures console as errors): https://github.com/getsentry/sentry-javascript/blob/develop/packages/core/src/integrations/captureconsole.ts
• @sentry/browser - breadcrumbsIntegration (captures console as breadcrumbs): https://github.com/getsentry/sentry-javascript/blob/develop/packages/browser/src/integrations/breadcrumbs.ts
• @sentry/deno - denoIntegration (captures console as breadcrumbs): https://github.com/getsentry/sentry-javascript/blob/develop/packages/deno/src/integrations/breadcrumbs.ts

the instrumentConsole utility:

sentry-javascript/packages/utils/src/instrument.ts

Line 109 in 5df78df

function instrumentConsole(): void {

Previous: #4532

[linear]

JS-956 Unify console instrumentation to a single integration

[Lms24]

Posting a longer version of my review comment here as well:

Our ideal end state is a single console integration that captures breadcrumbs by default, captures logs if enableLogs is set to true, and optionally captures errors if configured by users.

I'm not sure if it makes sense to do this with us more recently rather splitting integrations into single-purpose integrations than doing the inverse. I personally find captureConsoleIntegration for example pretty useless and never enable it, so I'm not sure if we always want to include the respective bundle size hit in browser, if users e.g. only want logs. This probably also depends on our long-term plan for breadcrumbs.