Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃檹 How can I exclude or avoid collecting chrome extension's error? #2534

Open
hongsiflearn opened this issue Dec 20, 2023 · 2 comments
Open

Comments

@hongsiflearn
Copy link

What are you trying to achieve and what is your issue? Please describe.
How can I exclude or avoid collecting chrome extension's error? Is there any option for this like Sentry provided?
image

Describe the solution you'd like

  • option for avoid collecting chrome extension's error in initConfiguration from datadogRum.init function
  • or some if statement inside beforeSend, maybe

Describe alternatives you've considered

@hongsiflearn hongsiflearn changed the title 馃檹 My support need 馃檹 How can I exclude or avoid collecting chrome extension's error? Is there any option for this like Sentry provided? Dec 20, 2023
@hongsiflearn hongsiflearn changed the title 馃檹 How can I exclude or avoid collecting chrome extension's error? Is there any option for this like Sentry provided? 馃檹 How can I exclude or avoid collecting chrome extension's error? Dec 20, 2023
@amortemousque
Copy link
Contributor

amortemousque commented Dec 20, 2023

Hello @hongsiflearn,
Thanks for your feedback. Do you have a minimal reproducible example to test this behaviour? Also what is the Sentry option you are referring to?

In any case, like you mentioned, you could probably filter out these errors with the beforeSend API using the context parameter. In case of RUM Error, the context parameter contains the original error which would allow you to check the context.error.stack.

@hongsiflearn
Copy link
Author

Do you have a minimal reproducible example to test this behaviour?

No 馃槪

Also what is the Sentry option you are referring to?

processing > Inbound Filters
image (20)

In any case, like you mentioned, you could probably filter out these errors with the beforeSend API using the context parameter. In case of RUM Error, the context parameter contains the original error which would allow you to check the context.error.stack.

Thanks, I will try it !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants