Issue
I see the option to delete issues. When should I use them?
Applies To
- All Plans
- Error Monitoring
- Issues
Resolution
Deleting all your issues to just get rid of them may be tempting, but in many cases it’s a temporary fix, and there are better solutions. If none of the situations below apply, it might be appropriate to delete the events.
Issues are grouped together based on the algorithms shown here. You can set up SDK fingerprinting to override the default grouping, or look at the Fingerprint Rules (Server-side fingerprinting) and Stack Trace Rules (Grouping enhancements).
After setting this up, you may want to merge the previous issues together to clean up the UI.
You can filter out a number of commonly unwanted issues from the UI by navigating to your Project > Settings > Inbound Filters.
Most of our SDKs support custom filtering. Read how to configure your SDK to determine which events to send/not send here.
If you are on our Business Plan, you can also use the Delete & Discard option. This will filter out future matching events, and is a reversible action.
You may want to resolve the issues instead, which can be helpful if you want to search for them later on.
Deleting an issue won’t affect your quota, as it’s already been processed by Sentry. You can find a quick guide on what counts towards your quota here.
This depends on the type of the event:
- Errors: It is best to delete the issue as instructed here. It is not possible to delete an individual error, so you will have to delete the whole issue.
- Transactions/spans, replays, profiles, user feedback, logs: Unfortunately, it is not possible to delete these types of events. If you really need to delete this information, you will have to delete the whole project. You can do so by going to the project's settings > General settings > click on "Remove Project" at the bottom of the page.
Note: While deleting logs is not possible during beta, we have plans to implement this in the future.