Load latest sentry errors instead of loading the full error list everytime
Problem to solve
If a user regularly uses the error list to triage errors in their day to day, it can become immediately out of date. Surfacing a link at the top of the table telling the user that there are new errors, give them awareness and allows them to refresh the table at a time that is convenient to them versus changing the page as new ones come in, ripping them out of context and losing their place on the page.
This is a UX improvement that may be implemented as part of #32464 (closed).
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
Further details
This work supports the Error Tracking Vision.
Proposal
From: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24806?view=parallel#note_143855826
When polling fetches new Errors from backend, a row should be added to the top of the list saying "Show latest Sentry errors". Clicking the button updates the table.
Permissions and Security
Documentation
Not required.
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Activity
Simon mentioned in this https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24806?view=parallel#note_143857114 something about this feature existing prior to this follow up issue, but from the commit history I can't for the life of me find where was this implemented
Edited by Jose Ivan Vargas@jivanvl apologies for poor wording. I meant that polling existed before (i.e. we are using
Poll). We haven't had any UI to update it, so currently it just flashes the new rows in.So I meant we still poll, but prompt with the button/text before we show the latest data in the UI. Better text is maybe "Show latest Sentry errors" rather than "Load".
added devopsmonitor typefeature labels
added Health label
changed milestone to %FY20 Q3
added [deprecated] Accepting merge requests label
changed milestone to %12.4
added grouprespond label
removed Health label
changed milestone to %Backlog
added Category:Error Tracking label and removed 1 deleted label
changed milestone to %Backlog
@ameliabauerly I went digging through existing Error Tracking issues and found this one. I think it is a smart addition to the UX for the error tracking table - thoughts?
It can remain its own issue or we can include it in the scope of this one.
My concern with implementing the design as specified in the description is that it would be a bit of a temporary fix that we'd likely have to replace in the longer-term if we want to introduce additional sort options.
It seems like another approach here would be to introduce the sort functionality we already have in GitLab (for example, on the issue list page), as it will allow us to extend the sort on the error list page down the line without re-building anything.
If we build on the ideas we're working on #32464 (closed), we could introduce a sort dropdown after the search/filter field. Here's how that could look:
Sentry includes a sort for first seen, last seen, priority and frequency. I've just added first/last seen and frequency for now, but we could add priority, as well.
Thoughts on this, @sarahwaldner?
-
@ameliabauerly My impression of this issue was that it was solving for the scenario where users are triaging the list and new errors have come in while they are looking or while the browser is open to this page...they would get notification that new errors have come in without them automatically loading and getting ripped out of context. I agree that we need those filter options but that seems different than the scope of this issue? Please let me know if I am missing the point. thanks!
-
My impression of this issue was that it was solving for the scenario where users are triaging the list and new errors have come in while they are looking or while the browser is open to this page...they would get notification that new errors have come in without them automatically loading and getting ripped out of context.
I re-read through the description and comments on this issue, and I think you're right. I was imagining this was more about sorting the existing errors than the new ones coming in. But, I agree, this is primarily about the latter scenario.
I think this is a good idea, but we'd need to think a bit more about the visual piece here. We have an existing pattern for alerts (at the top of the page) but we don't currently have a pattern for alerts within tables. Since we'd effectively be creating a new visual pattern, we'd need a bit more investigation to figure out the right approach here.
It feels like this is a slightly lower priority change than the other Error Tracking issues we're working on for 12.5. Do you agree or would you like me to move this up the priority list? Wanted to ask the question so I'm focusing on the right things in this last week of 12.4.
Edited by Amelia Bauerly -
@ameliabauerly Let's consider this in 12.6 or 12.7. Do you think users are going to run into this problem? If not, I am happy to move it to the backlog or awaiting further demand.
-
I imagine they would run into this problem, but it seems like resolving this is probably less of a priority than some of the other changes we're discussing (like, having a more detailed error view, and allowing users to create issues from errors). I think adding this as part of our 2nd pass of Sentry updates seems like a good idea
👍 -
@ameliabauerly I have scheduled it for 12.7! And we can prioritize against the remainder of error tracking work when we get there.
changed milestone to %12.5
mentioned in issue gitlab-org/monitor/general#36 (closed)
added UX designideation labels
changed milestone to %12.6
changed milestone to %12.7
changed milestone to %Backlog
added sectionops label
added groupobservability label and removed grouprespond label
