Last updated:

Project Monitoring Overview

This section introduces how to view monitoring information on the project overview page.

For other information on the project overview page, see Project Overview.

Prerequisites

You should join a workspace and have the Monitoring Viewing permission within the workspace. For more information, refer to "Workspace Members" and "Workspace Roles".
WhizardTelemetry Monitoring should have been installed and enabled.

Steps

Click Overview in the left navigation pane.

The Overview page provides the following monitoring information:

Area	Description
Resource Usage	The total and real-time usage of CPU, memory, and disk for the current project.
Pods	The number of various types of pods in the current project. Pod status includes: Running: The pod has been assigned to a node, all containers in the pod have been created, and at least one container is running, starting, or restarting. Pending: The pod has been accepted by the system, but at least one container has not been created or is not running. This state may indicate that the pod is waiting for scheduling or for the container image to be downloaded. Completed: All containers in the pod have terminated successfully (with an exit code of 0) and will not be restarted. Failed: All containers in the pod have terminated, and at least one container has terminated with a non-zero exit code. Unknown: The system is unable to get the status of the pod. This state usually occurs when the system fails to communicate with the host where the pod is located. Pod QoS (Quality of Service) types include: Guaranteed: Each container in the pod has memory limits, memory requests, CPU limits, and CPU requests, and the memory limit is equal to the memory request, and the CPU limit is equal to the CPU request. Burstable: At least one container in the pod does not meet the requirements of the Guaranteed type. BestEffort: Containers in the pod do not configured with any memory limits, memory requests, CPU limits, or CPU requests. The QoS type of the pod determines the running priority of the pod. When resources in the system is insufficient to run all pods, the system gives priority to running pods of QoS type Guaranteed first, followed by pods of QoS type Burstable, and finally, pods of QoS type BestEffort.
Resource Usage Ranking	The top 5 workloads with the highest resource usage in the current project. Click the dropdown list to select sorting by CPU, memory, outbound traffic, or inbound traffic. Click / above the list to sort in ascending/descending order. Click View More below to view the resource usage details of workloads.

Area

Description

Resource Usage

The total and real-time usage of CPU, memory, and disk for the current project.

Pods

The number of various types of pods in the current project.

Pod status includes:

Running: The pod has been assigned to a node, all containers in the pod have been created, and at least one container is running, starting, or restarting.
Pending: The pod has been accepted by the system, but at least one container has not been created or is not running. This state may indicate that the pod is waiting for scheduling or for the container image to be downloaded.
Completed: All containers in the pod have terminated successfully (with an exit code of 0) and will not be restarted.
Failed: All containers in the pod have terminated, and at least one container has terminated with a non-zero exit code.
Unknown: The system is unable to get the status of the pod. This state usually occurs when the system fails to communicate with the host where the pod is located.

Pod QoS (Quality of Service) types include:

Guaranteed: Each container in the pod has memory limits, memory requests, CPU limits, and CPU requests, and the memory limit is equal to the memory request, and the CPU limit is equal to the CPU request.
Burstable: At least one container in the pod does not meet the requirements of the Guaranteed type.
BestEffort: Containers in the pod do not configured with any memory limits, memory requests, CPU limits, or CPU requests.

The QoS type of the pod determines the running priority of the pod. When resources in the system is insufficient to run all pods, the system gives priority to running pods of QoS type Guaranteed first, followed by pods of QoS type Burstable, and finally, pods of QoS type BestEffort.

Resource Usage Ranking

The top 5 workloads with the highest resource usage in the current project. Click the dropdown list to select sorting by CPU, memory, outbound traffic, or inbound traffic.

Click / above the list to sort in ascending/descending order.
Click View More below to view the resource usage details of workloads.

Feedback

Was this page Helpful?

Receive the latest news, articles and updates from KubeSphere

Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.

Previous : Workspace Monitoring Overview Next : Cluster Status

What’s on this Page