### Problem to solve Our metrics dashboard provides a detailed view of individual metrics across single service; this view does not scale, operators require a bird's-eye view across all of our services and IT infrastructure. ### Intended users * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal Provide a curated experience for operators to view the health of their infrastructure * Compact view which visualizes the health of our infrastructure * Scale to 1K+ infrastructure items. * Native support for container orchestration frameworks. * Group by Namespace, cluster, pod * ability to view Pod and containers health ### User flow As a user, I would like to view the health across all of my pods * Infrastructure dashboard would show a view of pods group by namespace, cloud providers, hosts * User should be able to select the environment to look at * User can select the metric which spans across all pods (e.g., CPU, memory usage) * User should be able to drill directly into logs for the specific pod * User should be able to drill into metrics of a specific pod ### Design In this issue, we are proposing adding two additional views to the current Operations > Environments page. In addition to the deployments view (which already exists), we are also proposing adding a pod health view, and a metrics view: | Deployments view | Pod health view | "Metrics" view | | ------ | ------ | ------ | |  |  |  | Clicking on any of the pods in any of the visualizations above, will allow users to view either the logs or the metrics for the selected pods. Here's an example of how that could look: | User clicks on pod and decides what to view | Drilling down to a pod's log | Drilling down to a pod's metrics | | ------ | ------ | ------ | |  |  |  | Proposal is to show the log view by default. Note: we are also proposing adding a legend to the current deployments view. Apparently there are six or seven statuses that will need to be represented within the key, but it's not clear how those statuses are represented currently. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g., email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references [Sketch cloud](https://sketch.cloud/s/ddmJn)