[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-01。"],[],[],null,["With fleet team management, you can view team-scoped information such as resource utilization aggregated by team and by namespace, enabling you to\noptimize spending and resource allocation. The **Monitoring** tab within the **Teams** page in the Google Cloud console provides an overview of a specific team scope in your fleet.\n\nThis page assumes that you are familiar with resource management in Kubernetes.\nIf you need to learn more, see [Resource management for Pods and\ncontainers](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/)\nin the Kubernetes documentation.\n\nView the dashboard\n\nTo view the Monitoring dashboard:\n\n1. With your [fleet host project](/kubernetes-engine/fleet-management/docs/fleet-concepts#fleet-host-project) selected, go to the **Teams** section in the Google Cloud console.\n\n [Go to Teams](https://console.cloud.google.com/kubernetes/teams/)\n2. In the **Teams** page, select the team scope whose details you want to view, and then click the **Monitoring** tab.\n\nSelect a time filter\n\nBy default the team scope overview shows resource utilization over the past seven days. To change this time window, use the time filter options at the top of the page:\n\n- Select the time window over which you want to view the average resource utilization of the scope containers. Choose one of the predefined options, or select **Custom** to specify a custom time window.\n\nView team summary\n\nThe row below the time filters provides an at-a-glance view of your team scope including the number of clusters and namespaces, and total resource utilization over time. Resource utilization metrics are generated using [Cloud Monitoring](/monitoring/docs/monitoring-overview) data from your team's clusters. This section shows you:\n\n- The number of clusters and namespaces associated with the team. Click **View all clusters** or **View all namespaces** to see your team's full cluster or namespace list.\n- The number of errors in the team scope, if any. If an error is displayed, click **View in error logs** to get more details in the Logs Explorer.\n- The number of restarts across containers for your selected time interval. Click **View in restart logs** to view more details in the Logs Explorer.\n- The estimated monthly cost for the team scope. Click **View in Cost Optimization** to see more detailed [cost-related utilization metrics](/kubernetes-engine/docs/how-to/cost-optimization-metrics) for the scope.\n- The average amount of CPU, Memory, and Disk utilization across namespaces for the selected time interval. For more information, see [Fleet resource utilization metrics](/kubernetes-engine/fleet-management/docs/utilization-metrics).\n\n| **Note:** If you have newly-created clusters in your team scope, depending on the time window you have chosen, you may not see any data in the **Total Utilization** card and the rest of the dashboard. For more information, see [Fleet resource utilization metrics](/kubernetes-engine/fleet-management/docs/utilization-metrics#troubleshooting).\n\nView detailed resource utilization\n\nThis section provides a detailed view of how your team is using its resources, including resource utilization by team, and top resource utilization by namespace. You can read about how these metrics are calculated in more detail in\n[Fleet resource utilization\nmetrics](/kubernetes-engine/fleet-management/docs/utilization-metrics).\n\nView resource utilization over time\n\nThe **CPU/memory/disk utilization by team** sections show how your team uses resources over time, and how the clusters within your scope request resources compared with the set resource limits. Each panel shows a graph of your team-aggregated CPU, memory, or disk usage over the time window you have chosen, with the following information displayed as separate lines:\n\n- **Limit**: The maximum amount of the resource that containers across your team scope are allowed to use, for example, 42.5 CPUs.\n- **Requested**: The amount of the resource that containers across your scope have requested, for example, 3.8 CPUs.\n- **Used**: The actual amount of the resource that your containers used, for example, 0.64 CPUs.\n\nTo 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 resource limit, and requested and actual resource usage information for that time is displayed.\n\nTo toggle the display of one or more of the lines in the chart, click the relevant metric or metrics below the graph.\n\nView top resource utilization by namespace\n\nThe **Top CPU/memory/disk utilization by namespace** row shows you the five namespaces that are the biggest users of their resources. Each panel lists your top namespaces in order of utilization (highest first). For each namespace, you can see both a graph of their usage of the resource, and an average of their resource usage relative to the resource limit, and used and requested resources over the chosen time window. This view can help you, for example, to see namespaces that are overutilized.\n\nTo view resource utilization for all your namespaces for your chosen time window, click on **View all namespaces by CPU/memory/disk utilization**.\n\nView error distribution by namespace\n\nThis card indicates the namespaces with the most error logs for the time window you have chosen. To view log details, click on **View all errors in Cloud Logging**.\n\nView restart counts distribution by namespace\n\nThis section shows you the namespaces with the highest number of container restarts for the time window you have selected. This can help you assess, for example, if you need to adjust the CPU limit and requested CPU amount if a container has restarted because of CPU usage. To view log details, click on **View all restarts in Cloud Logging**."]]