ZStack ZSphere Documentation
All Version
All
ZStack ZSphere 4.10.6>ZStack ZSphere Documentation>ZStack ZSphere User Guide>O&M Management>Resource Monitoring
Get PDF

O&M Management


Resource Performance Monitoring


Overview

ZStack ZSphere provides visual charts that display various monitoring data for resources over a period of time. These charts include multiple key performance monitoring metrics, helping you gain an intuitive understanding of resource performance conditions.

Monitoring Chart Types

Chart Type Description
Bar Chart Displays monitoring data of resource capacity load in the form of proportional bars, providing an intuitive understanding of resource capacity information.
Line Chart Displays monitoring data of various loads on resources in the form of a line chart, offering an intuitive understanding of resource health status.

Monitoring Data Collection Methods

ZStack ZSphere provides two monitoring methods for virtual machines. Generally speaking, for memory data, Advanced Monitoring offers better accuracy than Basic Monitoring. It is recommended to use Advanced Monitoring when monitoring memory data.
  • Basic Monitoring: Monitoring data is obtained from the host via Libvirt.
  • Advanced Monitoring: Monitoring data is obtained from the virtual machine by an advanced monitoring agent. VMTools must be pre-installed on the virtual machine for this method.

Monitoring Data Collection Intervals

ZStack ZSphere uses real-time monitoring, with resource monitoring charts refreshing data every 10 seconds by default.


Capacity Monitoring

ZStack ZSphere provides information on the usage and allocation of various computing and storage resources, including virtual machines, hosts, clusters, data storage, data centers, and root nodes (management nodes). This allows you to comprehensively understand the platform's resource usage from both micro and macro perspectives.

Capacity Monitoring Metrics

You can go to the overview details page of the corresponding resource to understand the platform's resource usage from the Capacity Information card. The following table lists the detailed monitoring metrics for various resources.

Object Monitoring Metrics and Description
Root Node
  • CPU: Total physical CPU GHz and average utilization rate across all data centers.
  • Memory: Total physical memory, average utilization rate, and remaining available capacity across all data centers.
  • Storage: Total physical storage, average utilization rate, and remaining available capacity across all data centers.
Data Center
  • CPU: Total physical CPU GHz and average utilization rate within the data center.
  • Memory: Total physical memory, average utilization rate, and remaining available capacity within the data center.
  • Storage: Total physical storage, average utilization rate, and remaining available capacity within the data center.
Data Storage
  • Storage Utilization: Total storage resources, utilization rate, and remaining available capacity.
  • Storage Allocation Ratio: Allocation status of storage resources.
  • Storage Distribution: Distribution of storage resources, including: total capacity after overcommitted, reserved capacity, allocated capacity (such as snapshot capacity, image cache, migration storage, virtual machine disk capacity.), and remaining allocatable capacity.
Cluster
  • Resource Utilization: Total physical CPU and memory resources, utilization rate, and remaining available capacity in the cluster.
  • Resource Allocation Ratio: Allocation status of physical CPU and memory resources in the cluster.
  • Resource Distribution: Distribution of CPU and memory resources after overcommitted in the cluster, including: total capacity after overcommitted, reserved capacity, allocated capacity, and remaining allocatable capacity.
Host
  • Resource Utilization: Total physical CPU, memory, and storage resources on the host, utilization rate, and remaining available capacity.
  • Resource Allocation Ratio: Allocation status of CPU, memory, and storage resources on the host.
  • Resource Distribution: Distribution of CPU, memory, and storage resources after overcommitted on the host, including: total capacity after overcommitted, reserved capacity, allocated capacity, and remaining allocatable capacity.
Virtual Machine
  • CPU: Number of CPU cores and utilization rate for the virtual machine.
  • Memory: Total memory capacity, used capacity, and remaining available capacity for the virtual machine.
  • Storage: Total storage capacity, used capacity, and remaining available capacity for the virtual machine.

Capacity Calculation Rules

Category Calculation Rules
Resource Utilization Rate Total CPU = Physical Cores × Single-Core GHz
Resource Allocation Ratio
  • Allocation Ratio = Allocated : Total Overcommit Capacity
  • Total Overcommit Capacity = Physical Total − Reserved Physical Capacity
  • Total Allocatable = Total Overcommit Capacity × Overcommit Ratio
  • Free to Allocate = Total Allocatable − Allocated
Resource Distribution CPU
  • CPU Overcommitted Total = Physical CPU Total × Overcommit Ratio
Memory
  • Memory Overcommitted Total = Reserved Memory + Total Allocatable Memory Capacity
  • Total Allocatable Memory = (Physical Memory Total − Reserved Memory) × Overcommit Ratio
Storage
  • Storage Overcommitted Total = Reserved Capacity + Total Allocatable Storage Capacity
  • Total Allocatable Storage = (Physical Storage Total − Reserved Capacity) × Overcommit Ratio
The meaning of overcommitment and allocation are as follows:
  • CPU Overcommitment: This indicates that a single physical CPU core can be virtually divided into N logical CPU cores for allocation to virtual machines.

    For example, if the CPU overcommitment ratio is 2:1, then one physical CPU core can be virtually divided into 2 logical CPU cores. Therefore, if a host has 10 physical CPU cores, it can be virtually divided into 20 logical CPU cores for allocation to virtual machines.

  • Memory/Storage Overcommitment: This indicates that a unit of memory/storage capacity can be virtually expanded into N units of memory/storage capacity for allocation to virtual machines.

    For example, if the memory/storage overcommitment ratio is 2:1, then 1 GB of memory/storage capacity can be virtually expanded into 2 GB. Therefore, if a host has 100 GB of memory/storage, it can be virtually expanded into 200 GB for allocation to virtual machines.

  • CPU Allocation: This indicates that a physical CPU core is actually virtually divided into N logical CPU cores for use by virtual machines. Therefore, the CPU allocation ratio ≤ CPU overcommitment ratio.

    For example, if the CPU allocation ratio is 1.5:1, then one physical CPU core is actually virtually divided into 1.5 logical CPU cores. Therefore, if a host has 10 physical CPU cores, they have actually been virtually divided into 15 logical CPU cores for allocation to virtual machines.

  • Memory/Storage Allocation: This indicates that a unit of memory/storage capacity is actually virtually expanded into N units of memory/storage capacity. Therefore, the memory/storage allocation ratio ≤ memory/storage overcommitment ratio.

    For example, if the memory/storage overcommitment ratio is 1.5:1, then 1 GB of memory/storage capacity is actually virtually expanded into 1.5 GB. Therefore, if a host has 100 GB of memory/storage, it has actually been virtually expanded into 150 GB for allocation to virtual machines.

Using host storage as an example, if the total physical storage capacity is 100 GB, the reserved physical capacity is 10 GB, the overcommitment ratio is 2:1, and the allocated capacity is 150 GB, then:
  • Storage Allocation Ratio = 150 GB : 90 GB = 1.67
  • Total Overcommit Storage = 100 GB - 10 GB = 90 GB
  • Total Allocatable Storage = 90 GB × 2 = 180 GB
  • Remaining Allocatable Storage = 180 GB - 150 GB = 30 GB





Archives

Download Document Archives

Products

Solutions

Help & Support

Contact Us

Site Terms  Privacy Policy  Rules and Conventions on User Management

© 2024, Shanghai Yunzhou Technology Co.,Ltd. (云轴科技). 沪ICP备15055560号-6

Back to Top

Download

Already filled the basic info?Click here.

Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

An email with a verification code will be sent to you. Make sure the address you provided is valid and correct.

同意 不同意

I have read and concur with the Site Terms 、 Privacy Policy 、 Rules and Conventions on User Management of ZStack Cloud

Download

Not filled the basic info yet? Click here.

Invalid email address or mobile number.
同意 不同意

I have read and concur with the Site Terms 、 Privacy Policy 、 Rules and Conventions on User Management of ZStack Cloud

Email Us

contact@zstack.io
ZStack Training and Certification
Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

同意 不同意

I have read and concur with the Site Terms 、 Privacy Policy 、 Rules and Conventions on User Management of ZStack Cloud

Email Us

contact@zstack.io
Request Trial
Enter at least 2 characters.
Invalid mobile number.
Enter at least 4 characters.
Invalid email address.
Wrong code. Try again. Send Code Resend Code (60s)

同意 不同意

I have read and concur with the Site Terms 、 Privacy Policy 、 Rules and Conventions on User Management of ZStack Cloud

Email Us

contact@zstack.io

The download link is sent to your email address.

If you don't see it, check your spam folder, subscription folder, or AD folder. After receiving the email, click the URL to download the documentation.

The download link is sent to your email address.

If you don't see it, check your spam folder, subscription folder, or AD folder.
Or click on the URL below. (For Internet Explorer, right-click the URL and save it.)

Thank you for using ZStack products and services.

Submit successfully.

We'll connect soon.

Thank you for using ZStack products and services.