-
Notifications
You must be signed in to change notification settings - Fork 41
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
[feature-request] Allow ignoring errors by Error type #55
Comments
Hi, @pedromss I've since moved to other providers so not actively using Bugsnag anymore. |
Does it? Are changes introduced in #40 not working? |
You're correct, I made a mistake in the report. Its not a 404, its a |
Hey @pedromss ,
So, I guess my question
still stands. |
I noticed that out of the box Plugsnag reports
404Phoenix.Router.NoRouteError
errors. I would like to request a feature that allows not reporting based onstatus codeexception. I can't see a use case for wanting to report404NoRouteError
as a bugsnag because anything can trigger a404NoRouteError
so if someone were to spam our system with routes we don't have we'd essentially be bleeding out Bugsnag quota.From the docs, there didn't seem to be a way around this, I only say the custom error builder, but I might have missed something.
Let me know if you're open to this and if you'd like me to take a shot at it.
The text was updated successfully, but these errors were encountered: