< img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3131724&fmt=gif" />

查看项目监控概览

本节介绍如何查看项目概览页面的监控信息。

有关项目概览页面的其他信息,请参阅查看项目概览信息

Prerequisites

  • You should join a workspace and have the 监控查看 permission within the workspace. For more information, refer to "Workspace Members" and "Workspace Roles".

  • KubeSphere 平台需要安装并启用 WhizardTelemetry 监控扩展组件。

Steps

  1. Log in to the KubeSphere web console with a user who has the 监控查看 permission, and access your project.

  2. Click 概览 in the left navigation pane.

    概览页面提供以下监控信息:

    功能区 描述

    资源用量

    当前项目的CPU、内存、磁盘的总量和实时用量。

    容器组

    当前项目的各种类型容器组的数量。

    容器组状态类型包括:

    • 运行中:容器组已分配给某个节点,容器组中的所有容器都已被创建,至少有一个容器正在运行、启动或重启。

    • 等待中:容组器已被系统接受,但有至少一个容器尚未创建也未运行。此状态下,容器组可能正在等待调度,或等待容器镜像下载完成。

    • 成功完成:容器组中的所有容器都成功终止(以 0 退出码终止),并且不再重启。

    • 失败:容器组中的所有容器都已终止,并且至少有一个容器以非 0 退出码终止。

    • 未知:系统无法获取容器组状态。出现这种状态通常是由于系统与容器组所在的主机通信失败。

    容器组 QoS(服务质量)类型包括:

    • 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.

    资源用量排行

    当前项目中特定资源用量最高的 5 个工作负载。点击下拉列表可选择按 CPU、内存、出站流量或入站流量排序。

    • 在列表上方点击sort-ascending/sort-descending 可按升序/降序排序。

    • 点击下方的查看更多,查看工作负载的资源用量详情。

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.

What’s on this Page