GitLab Protect Stage, 8 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Defend ux: alerts MVC threat monitoring

Description

design review for alerts MVC (threats monitoring): https://gitlab.com/groups/gitlab-org/-/epics/3438

A

Hey just working on this, you see on the designs and based on the what we want to show on the initial NBC, the name of the alert the date time, the cluster, possibly the environment and then the ability to filter by certain criteria and the action of being able to dismiss the design of very heavily revolved around the existing alert section here in operation alerts, and the goal is: is this solves a lot of problems that we want to do for the NBC in terms of design?

A

It's more consistent with the pattern found here and also, hopefully lower costs. So we can reuse what we see here so translating that then, first is the information architecture.

A

Originally in the earlier designs, we had an idea of showing it in the overview, but we opted out for that because maybe later this evolved to more, like a summary view, given all the follow-up issues, I think it's a better decision that we have it here in the second order tab and then next we see the table here which is very similar to alerts.

A

Hopefully, we can just basically adopt it and it starts by defaulting to the most recent alerts, so in the sort border here again, where we're taking it from this table. Something notable here is that it. It shows it by one day, two day days and then week and then months and then multiple months and then years if we could adopt that as well and then, notably there's a timestamp when you hover over. That shows you exactly when this alert occurred.

A

That the next part is the filtering, so in the requirements we wanted to filter by cluster environment policy, name and policy date and time I think for the MVC, the policy, the sort can help us by date and time, so we don't need a filter initially for that, and then the policy name could do that and the environment.

A

The outstanding question is about cluster, but I'll come back to that in just a minute: the environment and policy name, looking at how that filter works so showing it all by default and then filtering down from there seems like the ideal direction, at least for the start here, so that users can see multiple environment at once and the filters that I'm taking here come from the security dashboard pattern where it defaults to all, and then the user can multi-select.

A

So we can adopt this pattern, this component as well. For this, the other, the last part, is or two more parts actually questions about cluster on the Sam to speak. To that a little bit more but I know we had questions and then needed some feedback about how, if and how we can display it and then further filtering and by it it's shown here and the designs is displaying what the cluster is.

A

We didn't include the the filter, but just any thoughts or feedbacks on that, if it's within the scope of this MVC or if there's any challenges there to displaying that the last thing is the one action that the user can take to this page is to dismiss it so I. Wouldn't the thinking is so far and I'm not sold on it, but each one has a dismiss button and then the user can also undo dismiss and when they dismiss it, we could put like 50% opacity on the table row.

A

This is sort of a temporary solution, but it is also kind of aiming for the long term of on the alert section to make an action.

A

We we see this right now, and this could also be something that we adopt, especially given there's a number of upcoming statuses that that may be following up with this, including adding an issue. Maybe that would be a breakout button or some other way, but just as a start to to kind of show that the actions are located here, and this is the first one, it's the simple dismiss and undo dismiss. The ability to undo dismiss is also seen in the merge requests.

A

So no, not perfect, but it could be kind of like that. You know with given the follow-up issues sort of the little action hub over here to the far to the far right. Maybe we could add a header to that that has actions related.

A

It just depends on the exact actions that are coming down the road okay, so that pretty much is the current design state of this. Please, let me know if there's any thoughts or questions or suggestions to improve this yeah. Okay, thank you.