apache / apache/cloudstack

Disk usage metrics do not work in specific zone

Open
#9,671 2 comments 0 reactions 0 assignees View on GitHub
affects:4.18 component:kvm component:metrics component:vmware
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

##### ISSUE TYPE

* Other

##### COMPONENT NAME

~~~
VMWARE
~~~

##### CLOUDSTACK VERSION

~~~
4.18
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

##### SUMMARY
In my environment, I use 2 zones.

However, in the "x" zone, the metrics part presents a problem when displaying disk and network data.

While in zone "y" all data is shown normally.

Do you have any specific connectivity tests to do?

In principle, the zone settings are identical, the only difference is the following:

Zone X
System VM's -> KVM (The only KVM it has are the two SystemVM)
Zone X environment uses VMware vSphere Client version 6.7.0

Zone y uses the system VM and entire environment with vSphere Client version 7.0.3.01700

##### Remembering that the disk and network metrics just do not appear in the problem area, but the CPU and memory metrics work normally.

Zone X:
![image](https://github.com/user-attachments/assets/7e64043f-470e-40ad-ba82-b49baeb4c157)

Zone Y:
![image](https://github.com/user-attachments/assets/b96dee72-c299-4589-a8ed-c8558de8fd60)

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by reproducing the metrics view in the two zones and comparing the VMware vSphere 6.7.0 and 7.0.3.01700 environments, focusing on why disk and network data are absent while CPU and memory appear. Done means identifying and correcting the cause so all four metric types display in zone X.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure, observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.