Allow estimated wait time to be filtered by a specific runner by description or ID

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Insight

Users wanted to see the estimated job wait per runner rather than by a group of runners. People manage their runners differently, but some orgs use runner descriptions to organize and identify them. Just like others use tags.

Supporting evidence

I would expect once you get onto this guy you should be able to see its individual. I wouldn't be able to see it out here, but once you go into this one and I think that would be helpful. Again, like a graphical thing to answer what I was just talking about would be the best way to view it. Cuz with the little graph you can see it instantaneously rather than trying to make sense of all the numbers and everything. Yep. Okay. At this level this makes sense to me, but this I think also would be helpful down at the low level to the individual ones. Yeah. And then I don't know if it would be difficult but it, I'm trying to think, I would think it'd be helpful to have it available here too, based on your filtering.

So trying to think of like as if I'm managing this, what would I then do you know, would I create more capacity with those types of runners? I would assume that would be what I'd be looking at doing. So one thing that comes to mind like is this a one-time thing or is this happening often? So how do I figure that out? Oh, like how busy is that runner over a period, like a long period of time. Yeah like if this is a, you know, Friday afternoon thing that it's no big deal that this guy is busy and maybe their wait times are up fine. But if this is happening every single day and slowing people down every single day, then I need to worry about it.

Maybe this one, the graph by looking at the graph, like how, what is the like wait time for to reach a specific runner in a fleet, which is if the response time is late, that I think then I will say that that particular runner is, I don't know whether I can pinpoint a specific runner.

from the Dash dashboard point of view, I would definitely like to highlight that when this happens. Yeah, we would still be interested in looking at the, you know, as I mentioned on the group stats here, when if we have a option to search by group or search by description, we would still be interested in consolidating the report for all of the runners on a certain group or project.

Well, tags is one thing, but obviously we don't have control over tags. That's another thing I, I, I don't know. Yeah. We, we, we don't have the control over tags, right? So we, we have certain tags that we are using on centrally managed runners, but we can't stop users or developers from using the same tag on their own specific runners as well. So, okay. Currently, currently it is based on the naming convention. You can say that we are, we are including our resource names in the description and we can filter out based on that.

Action

  • Add a filter by individual runner description/ID
  • Maybe add this to runner details too

Resources

Tasks

  • Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher.
  • Add the appropriate Group (such as ~"group::source code") label to the issue. This helps identify and track actionable insights at the group level.
  • Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project.
  • Adjust confidentiality of this issue if applicable
Edited by 🤖 GitLab Bot 🤖