Last updated:

Cluster Status Overview

This section introduces how to view the cluster status.

Prerequisites

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

Steps

Log in to the KubeSphere web console with a user who has the Monitoring Viewing permission, and access your cluster.
Click Monitoring & Alerting > Cluster Status in the left navigation pane.

View the status of cluster nodes, cluster resources, etcd, and service components under the Overview tab of the Cluster Status page.

Parameter	Description
Cluster Node Status	The total number of nodes in the cluster and the number of normal nodes.
Cluster Resource Usage	The total and used amounts of CPU, memory, and disk resources in the cluster, as well as the total number of pods that can be created in the cluster and the number of pods already created. By default, each normal cluster node can create a maximum of 110 pods.
etcd Monitoring	The service status, Raft proposal, database size, and client traffic of the etcd database. Service Status: Displays the Leader node of the etcd cluster, the IP address of each node, and the number of Leader changes in the last hour. Raft Proposal: Displays the number of committed, applied, failed, and pending Raft proposals per second. DB Size: The change in the size of the etcd database over time. Client Traffic: The data traffic sent to and received from gRPC clients. Viewing etcd monitoring information requires enabling etcd monitoring in advance. For more information, see the details page of the WhizardTelemetry Monitoring extension in the Extensions Center.
Service Component Monitoring	The request latency and requests per second of the Kubernetes API server, as well as the cumulative scheduling attempts and scheduling times per second of the scheduler.

Parameter

Description

Cluster Node Status

The total number of nodes in the cluster and the number of normal nodes.

Cluster Resource Usage

The total and used amounts of CPU, memory, and disk resources in the cluster, as well as the total number of pods that can be created in the cluster and the number of pods already created. By default, each normal cluster node can create a maximum of 110 pods.

etcd Monitoring

The service status, Raft proposal, database size, and client traffic of the etcd database.

Service Status: Displays the Leader node of the etcd cluster, the IP address of each node, and the number of Leader changes in the last hour.
Raft Proposal: Displays the number of committed, applied, failed, and pending Raft proposals per second.
DB Size: The change in the size of the etcd database over time.
Client Traffic: The data traffic sent to and received from gRPC clients.

Viewing etcd monitoring information requires enabling etcd monitoring in advance. For more information, see the details page of the WhizardTelemetry Monitoring extension in the Extensions Center.

Service Component Monitoring

The request latency and requests per second of the Kubernetes API server, as well as the cumulative scheduling attempts and scheduling times per second of the scheduler.

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 : Project Monitoring Overview Next : View Physical Resource Status

What’s on this Page