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
Filter TypeError - Load Failed by url #7275
Comments
Hi @jeengbe thanks for writing in! That's a tricky one, I agree.
I'm assuming you mean because bocking all "Load Failed" errors would also filter out your errors, not just the 3rd party ones, correct? Generally, errors without stack traces are a very hard problem to filter out correctly. We also don't have a good solution for that. This answer explains the reason for fetch errors without stacktraces quite well. This gave me an idea you could try but I can't guarantee that this solves it better:
This is just an idea. Can't tell you how this performs in practice. I hope this helps a little. |
Yeah, exactly. Wouldn't want to ignore real errors. 😄 I'll try to filter using breadcrumbs first, will come back with some insight. |
Appears to have worked. 🙂 Go through latest breadcrumbs and check if a blacklisted url has a failed request. |
@jeengbe could you please provide a code snippet on how you do this filtering? 🙂 |
Hi @KevinHerklotz, sure! |
Problem Statement
With 3rd-party tracking/ads software that doesn't try-catch their queries properly, we are seeing a lot of
with no further stack trace attached.
Since we can't really do anything about those errors and don't want them to eat up our error quota, we block them client-side.
This only works with errors that have a stack trace to the 3rd-party SDK attached to them, which these weirdly don't. What's the best way to filter them?
(This might not be relevant, but: )
Solution Brainstorm
The text was updated successfully, but these errors were encountered: