GitLab Plan Stage, 12 Jul 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab Value Streams Dashboard - Label filters demo

Description

Watch Alex Pennells from the Optimize team demonstrate how to filter and customize the Value Streams Dashboard comparison panel.

With this new configuration file, you can adjust the metrics comparison panel based on your areas of interest, filter out irrelevant information, and focus on the data that is most relevant to your analysis or decision-making process.

For more info: https://docs.gitlab.com/ee/user/analytics/value_streams_dashboard.html

A

So I'm here to give you a quick demo of the value streams, dashboard label search. So here we have an example page with the default view that you would see when you first load the page without any sort of configuration, set label search for a project, in this case the flight project, as well as the group search equivalent. So for the flight.js group and then the just an example of a search error that you would see if your labels that you filter by return, no results which I'll get into that more in a sec.

A

So so for this page in particular, this is the config that we're looking at. So we have the default panel right here, which is just includes the flight.js namespace, and that will render The View that you're used to seeing here and then over. Here we have the flight project filter, so we have the namespace, which is flight, JS flight and then the labels that we apply for the the search. So we have viper and XM, which you see reflected over here and then you'll notice, that the metrics that are returned are actually limited.

A

So uh whereas this one has deployment frequency time to restore change failure rate, this one is restricted to just these, even though we did not explicitly filter those or exclude those within our configuration file. Here.

A

This is due to the fact that these are the only metrics that currently support label filtering, so um we automatically restrict it to just those metrics as soon as you apply the label filter. That is expected, so don't wonder where all your metrics went, um except in addition to that. So if we keep scrolling down to the group search here, you'll notice that merge request throughput is actually missing from this dashboard, and that is because it still allows you to exclude additional metrics from the results.

A

So in this case, we specifically include merge, request throughput, which, in addition to all of the other ones, being excluded due to the label search being present, we're also excluding the throughput as well.

A

um So here you can see, there's only two labels. This one has a whole Squadron of labels that are being applied to the search.

A

um So one thing to note is that here we're filtering specifically on viper and XM, and we see that reflected here, but here we're just filtering on a which is a very simple search. So that's the important thing to note is that this is a search. This is not an exact keyword, so you can enter a short I can switch this to an E and then update that and then, when I reload, this page you're going to see quite a few different filters applied. So you can see it's already there.

A

So all of these now have an e on them. So it's it's more of a search, it's not an exact, so you can use it to fuzzy match labels that you want. If you have sub labels, you can occlude them all using uh just a parent and yeah, and then on top of that. So if you enter a search here at the bottom, that does not actually return any results.

A

So this this label does not exist at which points we'll try to load the label and with no labels loaded, we will immediately fail and the error will be present. So if you see that No Labels are being found, that's all of it so enjoy.