Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ignore unimportant Sentry errors
See original GitHub issueThere are some Sentry errors that Firefox clients will trigger which we can ignore. We should only ignore errors that do not degrade the user experience, ones that we don’t wish to spend time on fixing.
For example, if we can determine that this Oe is null error in photoswipe is not degrading the user experience then we should ignore it.
Non-Firefox clients produce tons of unimportant errors but let’s not worry about those for this issue.
We can ignore errors by using the ignoreErrors or ignoreUrls config options in RavenJS.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This sounds like a good idea to me. I agree it’s an issue that we get so many Sentry errors and tend to just ignore most/all of them. It makes Sentry a lot less useful.
Alright so we have releases now. I tried to delete the old events but we have too many and we can’t delete more than 1000 events at once… I enabled a feature that auto-hides events that haven’t been seen after 3 weeks. That should help reduce the number of events to look at.