-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Display discarded issue count and timestamp for each entry in "Discarded Issues" list in Sentry UI. #47755
Comments
Assigning to @getsentry/support for routing, due by Friday, April 21st at 5:00 pm (sfo). ⏲️ |
Routing to @getsentry/issue-experience for triage, due by Tuesday, April 25th at 1:37 pm (sfo). ⏲️ |
Routing to @getsentry/ingest for triage, due by Tuesday, April 25th at 17:00 (vie). ⏲️ |
I think this request is better routed to the ingest team, let me know if I'm wrong 🙏 |
Routing to @getsentry/telemetry-experience for triage, due by Wednesday, April 26th at 15:21 (vie). ⏲️ |
@Kobby-Bawuah thanks for suggesting this improvement.
do you mean how many events were discarded per issue? This issue is in our triaging backlog and we will discuss it soon 😉 |
Hi @priscilawebdev - Any update on this feature implementation? Numerous PCS customers have asked about this as of late. |
Hi @priscilawebdev - following up on this, has a priority been set for this feature? I've received further inquiries on how soon this can be available. |
Problem Statement
Could there be a way in the sentry website UI to know how many issues are being discarded for each individual entry in the “Discarded Issues” list? Or a way to see when a specific entry in that list was added?
Solution Brainstorm
Could add a count and timestamp column to the "Discarded Issues" list to make it easy for users to quickly see how many issues were discarded for each entry and when they happened.
Introduce a filter or search functionality for discarded issues to enable users to find specific entries and determine when they were added.
The text was updated successfully, but these errors were encountered: