-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi sentry instances #14000
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-issues for triage ⏲️ |
@ReneGreen27 if my understanding is correct, this issue appears to be an SDK issue. Could this be re-assigned? |
Hey @Amschi, could you try filtering all the integrations like this, otherwise your filters would probably have no effect: integrations: (defaultIntegrations) => [
...defaultIntegrations.filter(
(integration) =>
!["BrowserApiErrors", "Breadcrumbs", "GlobalHandlers"].includes(
integration.name,
),
),
happyIntegration(),
], |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
SaaS (https://sentry.io/)
What are you trying to accomplish?
Hi,
We are experiencing issues to setup sentry correctly when trying to follow this guide.
We have a multi module app. A main sentry is instantiated in an angular shell, I'm working with a react sub module and I would like to setup sentry on it.
Angular main app setup
React setup
How are you getting stuck?
With the current setup, parent module are leaking into sub project in sentry, meaning because of navigation we have error in sentry that are not related to our project.
According to the documentation, we should instantiate only one sentry client per js app, but If I do
this, i don't receive any event in sentry.
For now, we can do an ugly filtering with onBeforeSend callback, but I would prefer to understand what we are doing wrong here.
Thanks alot
Support would be appreciated.
Where in the product are you?
Issues
Link
No response
DSN
https://[email protected]/4508099137503232
Version
No response
The text was updated successfully, but these errors were encountered: