You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unify console instrumentation to a single integration #17702
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).
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.
Activity
linear commentedon Sep 18, 2025
JS-956 Unify console instrumentation to a single integration
Lms24 commentedon Sep 24, 2025
Posting a longer version of my review comment here as well:
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
captureConsoleIntegrationfor 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.feat(deno)!: Record console breadcrumbs via consoleIntegration
feat(deno)!: Record console breadcrumbs via consoleIntegration
feat(deno)!: Record console breadcrumbs via consoleIntegration
feat(browser)!: Record console breadcrumbs via consoleIntegration (#2…
feat(deno)!: Record console breadcrumbs via consoleIntegration (#24388)