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 these situations 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 enchancements).
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.
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. See What counts towards my event quota for more information.
Here’s a quick look at how Sentry handles your personal information (PII).
×We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII:
If you have any questions or concerns about your privacy at Sentry, please email us at compliance@sentry.io.
If you are a California resident, see our Supplemental notice.