From the scalability team, I'm going to talk to you a little bit about the stage group dashboard we've introduced a while ago. Every group that has a features running on gitlab.com also has a dashboard that represents how these features are doing. Performance, wise and popularity, wise and all of the dashboards are in this folder on grafana, and this is an example. This is the the dashboard for the source code group.

The first line shows you. The error. Budget error budget is a representation of how your features are performing and how your features are. The features for this group are contributing to um the availability of gitlab.com and there's also a dashboard for gitlab.com availability available in grafana and everything below that, and it's supposed to help people dig into how features are doing so. Then the first row below that is showing uh how many errors are contributing to the budget. With some some links to the logs with more detail.

The logs have more detail because we have more granular data available. There, uh then below is several graphs regarding requests or sidekick jobs and how many queries they're performed per action.

How many cash hits there are durations that kind of that kind of stuff, and all of this is default, but the dashboards are customizable, there's documentation on that available in the development documentation in our main repository, but if there's any problems with that um feel free to reach out the code for this lives in the the runbooks repository, which is also documented here below here um next will be adding um a way for groups to define their own indicators for um for their features.

So then the groups can tell the system itself how features are supposed to be performing how long a request can take. Some requests can be slower. Some need to be really fast. So that's coming next in this project, if there's anything feel free to reach out to us on on slack. Thank you very much.