This section describes how to view monitoring information on the workspace overview page.

Prerequisites

  • The WizTelemetry Monitoring extension must be installed and enabled on the KubeSphere platform.

Steps

  1. Log in to the KubeSphere web console with a user who has Monitoring Viewing permissions and enter your workspace.

  2. Click Overview in the left navigation pane.

  3. Click Resource Usage to view the usage of physical resources and application resources in the workspace.

    Area Description

    Physical Resources

    CPU and memory usage of the workspace in the specified cluster.

    Application Resources

    The number of Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, Persistent Volume Claims, etc., created by the workspace in the specified cluster.

    • Click timed-task in the upper right corner to set the time range.

    • Click start/pause in the upper right corner to enable/disable real-time data refresh.

    • Click refresh in the upper right corner to refresh data manually.

    • Click the Cluster dropdown in the upper right corner to view data for a specific cluster.

    • Click the line charts in Physical Resources and Application Resource Usage to view detailed information about resource usage over time. Select a project, click OK to view resource usage information for a specific project.

  4. Click Usage Ranking to view the resource usage of projects within the workspace.

    • Click the Cluster dropdown in the upper left corner of the list to view data for a specific cluster.

    • Click the dropdown above the list to sort projects by CPU usage, memory usage, pod count, outbound traffic, or inbound traffic.

    • Click sort-ascending/sort-descending above the list to sort in ascending/descending order.

    • Click Export in the upper right corner of the list to download resource usage data in JSON format.

  5. Click Cluster Information to view the total and used amounts of CPU, memory, and disk for clusters authorized to the workspace, as well as the total number of pods that can be created and the number already created on the cluster.

    Note

    By default, a maximum of 110 pods can be created per cluster node.