search

getsentry / sentry

Developer-first error tracking and performance monitoring
https://sentry.io
Other
38.63k stars 4.14k forks source link

Issue - Be able to automatically Archive issues based on certain Criteria #62258

Open Angelodaniel opened 9 months ago

Angelodaniel commented 9 months ago

Problem Statement

We have number of issues that happen due to the connectivity interruption. They all have the same feature - e.g. the message is “RestApiException{statusCode: null, error: Failure.}” or the response Body is empty.

We would not want to discard these events by the inbound filters, because we need to have the statistics built around those events, but we wouldn’t want to see these as new or ongoing issues. so for every issue that comes with this message we want to auto-archive it. Think of “skip inbox” feature of Gmail

Solution Brainstorm

Product Area

Issues

┆Issue is synchronized with this Jira Improvement by Unito

getsantry[bot] commented 9 months ago

Assigning to @getsentry/support for routing ⏲️

getsantry[bot] commented 9 months ago

Routing to @getsentry/product-owners-issues for triage ⏲️

snigdhas commented 8 months ago

Thanks, added to the team's backlog. I believe this is in the same space as some work we've been thinking about for upcoming quarters

MatthewMaclean commented 2 months ago

My org has been bumping into this too. There are some classic "Failed to fetch" network issues that are ungrouped as a result of the various locations they can occur. As a result, they trigger a variety of our monitors around "new issues" and "issues over a certain threshold", making monitoring a bit of a pain.

I definitely want to be able to see the volume of issues that meet that message, in case we have a user outage and it is correlated to the issue. It just happens that these errors are almost always false positives unless they exceed some threshold/anomaly.

garrettboatman commented 3 weeks ago

Would love to see this implemented 👀