## Release notes You can now easily visualize the state of runners in your environment. This release adds new visualizations to the runner admin view to simplify your runner fleet management experience. The admin area runners view now includes status badges with big, bold numbers so you can see at a glance critical data about your runner fleet status. **Note** for this release the values are static and won't change if you apply filters to the view. <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### 🧩 Problem It is difficult for an admin to come to the runners table and get an idea of how many runners are "OK" or "NOT OK" immediately. ### 💡 Proposal As a followup to https://gitlab.com/gitlab-org/gitlab/-/issues/344857, we should use the [Single Stat component](https://design.gitlab.com/data-visualization/single-stat) to add more runner statuses in the summary breakdown. We would like to have: - Online count - Offline count - Stale count [🎨 Designs in design management](https://gitlab.com/gitlab-org/gitlab/-/issues/346061/designs/Status-filters.png) [🖌 Figma prototype](https://www.figma.com/proto/BR7uFYXKi098NhwjnaR0cu/Runner-Enterprise-Management---Default-view?node-id=383%3A47607&scaling=min-zoom&page-id=383%3A46764&starting-point-node-id=383%3A47607) **Note:** We should move the count below the filter bar and update it as filters are applied, or as you move to other tabs. We can copy what is currently implemented here https://gitlab.com/gitlab-org/gitlab/-/value_stream_analytics to do so. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->