The Anthos overview in the Google Cloud console provides a "big picture" overview of your entire fleet. It provides a fleet-level view of your resource utilization that you can use to help optimize spending, application design, and resource allocation, including CPU, memory, and disk utilization aggregated by fleet and by cluster. It also shows fleet-wide Policy Controller coverage, helping you identify areas where you can improve security and compliance.
This page assumes that you are familiar with resource management in Kubernetes. If you need to learn more, see Resource management for Pods and containers in the Kubernetes documentation.
The Anthos overview in the Google Cloud console is available for fleet users who have enabled the entire Anthos platform only.
View the overview
To view the overview:
With your fleet host project selected, go to the Anthos overview in the Google Cloud console.
View clusters and resource utilization
The resource utilization section of the page provides a detailed view of how your fleet is using its cloud or on-premises resources, including resource utilization over time, and resource utilization by cluster. This can help you see, for example, where you have potentially underutilized or overutilized clusters that you might want to resize. You can read about how these metrics are calculated in more detail in Fleet resource utilization metrics.
Resource utilization metrics are generated using system Cloud Monitoring data from your fleet's clusters. See Enable system Cloud Monitoring for fleet clusters below if you see Missing data from... at the top of the page.
View cluster status
At the top of this section, you can see how many clusters are in your fleet, with warnings or errors displayed if there are any issues with their connectivity to the fleet: for example, if you have deleted a cluster without unregistering it first, or if you need to log in to a cluster outside Google Cloud to see its details.
- If an error or warning is displayed, click the notification to see the problem cluster or clusters and fix the issue.
- Click View all clusters to see your fleet's full cluster list.
View total resource utilization
Your fleet's Total CPU/memory/disk utilization shows a seven day average of all your fleet containers' actual CPU, memory, and disk usage relative to allocatable resources across cluster nodes in this fleet. Allocatable on a Kubernetes node is defined as the amount of resources that can be used by regular Pods on that node.
This view gives you a quick overview of your fleet's resource utilization and available resources, and can indicate possible issues to investigate further with more detailed metrics: for example, if total CPU utilization is very low, you can use the "by cluster" metrics below to identify clusters that could be resized.
View resource utilization over time
CPU/memory/disk utilization by fleet lets you dig deeper into how your fleet uses resources over time, and also lets you consider requested resources from your clusters in addition to allocatable resources and actual usage. Each panel shows a graph of your fleet-aggregated CPU, memory, or disk usage over the last seven days, with the following information displayed as separate lines:
- Allocatable: The amount of the resource that is allocatable across your fleet cluster nodes
- Requested: The amount of the resource that containers across your fleet have requested
- Used: The actual amount of the resource that your containers used.
To see details for a given point on the graph, scroll across the graph to the time that you are interested in (for example, a visible spike in actual usage on the graph). The allocatable, requested, and actual resource usage information for that time is displayed.
To toggle the display of one or more of the lines in the chart, click the relevant metric or metrics below the graph.
View resource utilization by cluster
The final resource utilization row shows your fleet's Top CPU/memory/disk utilization by cluster, letting you quickly see which specific clusters are the biggest users of their allocatable resources. Each panel lists your top clusters in order of utilization (highest first). For each cluster, you can see both a graph of their usage of the resource over time, and a seven day average of their resource usage relative to their allocatable resources. This view can help you, for example, to see clusters that are overutilized. Clusters that don't have enough resources available might not be able to schedule Pods.
Click on clusters that you're interested in to drill down further, including to see more node, workload, and service details in the GKE dashboards. This can help you see which workloads are affecting the cluster's resource usage.
View Policy Controller coverage
Policy Controller enables the enforcement of fully programmable policies for your clusters. These policies act as "guardrails" and prevent any changes to the configuration of the Kubernetes API from violating your organization's security, operational, or compliance controls. This dashboard section shows your fleet's overall Policy Controller coverage, including:
- How many clusters have Policy Controller enabled
- How many clusters have Policy Controller constraints configured that use the Google-provided constraint template library
- How many clusters have Policy Controller constraint violations
Click Enable Policy Controller to enable this feature on any clusters that aren't already using it. You can learn more about enabling and configuring Policy Controller in its documentation.
Enable system Cloud Monitoring for fleet clusters
As mentioned above, the metrics in the dashboard are generated using Cloud Monitoring data for system components (such as workloads in the
gke-connect namespaces), which means Cloud Monitoring must be enabled for each fleet member cluster for the overview to provide accurate usage information. Most GKE and Anthos clusters have Cloud Logging and Cloud Monitoring enabled by default. Attached clusters always require you to set up Cloud Monitoring manually.
If any of your fleet's clusters do not have Cloud Monitoring enabled, a panel is displayed at the top of the page showing the number of clusters with missing data. To enable Cloud Monitoring for system components on these clusters:
In the Missing data... panel, click View clusters to see the clusters that are not sending data to the Google Cloud console.
For each cluster in the list, see the following guide for your cluster type to enable Cloud Monitoring:
- Configuring Cloud Operations for GKE
- Use Cloud Logging and Cloud Monitoring with Anthos clusters on VMware
- Configuring Cloud Logging and Cloud Monitoring for Anthos clusters on bare metal
- Logging and monitoring for Anthos attached clusters
- Authorize logging and monitoring for Anthos clusters on AWS
- Authorize logging and monitoring for Anthos clusters on Azure
- Logging and monitoring for Anthos clusters on AWS (previous generation)
Enable monitoring for cross-project registered clusters
To gather and view metrics across multiple Google Cloud projects, Cloud Monitoring lets you create multi-project metrics scopes. When you register a GKE cluster from a different project to your fleet host project, a new metrics scope is automatically created that includes both projects (if it doesn't already exist). This lets you see utilization data from the cluster in the overview.
If you have existing cross-project registered GKE clusters and would like to see their data in the overview, follow the instructions in View metrics for multiple Google Cloud projects to manually create a new scope including the relevant project or projects.
- Learn more about the resource utilization metrics in the dashboard and how to use them in Fleet resource utilization metrics
- Learn more about using Cloud Logging and Cloud Monitoring to observe your clusters and their workloads.