[ZBX-19848] vmware.vm.memory.usage returns implausible values Created: 2021 Aug 23  Updated: 2024 Apr 10  Resolved: 2021 Oct 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 5.4.3
Fix Version/s: 5.4.6rc1, 6.0.0alpha4, 6.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Marco Hofmann Assignee: Michael Veksler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 10, Zabbix 5.2.7, VMware vCenter 6.7.0

Attachments: PNG File image-2021-08-23-15-19-48-396.png     PNG File image-2021-08-25-15-01-23-232.png    
Issue Links:
Causes
causes ZBX-20113 "vmware.hv.cpu.usage.perf[]" key retu... Closed
causes ZBX-20097 Add "celsius" support to vmware unitInfo Closed
Duplicate
Team: Team B
Sprint: Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021)
Story Points: 0.25

 Description   

List of problem metrics:

  • vmware.hv.cpu.usage.perf
  • vmware.hv.cpu.utilization
  • vmware.vm.memory.usage
  • vmware.vm.cpu.latency
  • vmware.vm.cpu.readiness
  • vmware.vm.cpu.swapwait
  • vmware.vm.cpu.usage.perf

Steps to reproduce:

  1. Link Template VMware to a vCenter instance
  2. Wait for LLD
  3. Check latest data of discovered VMs with linked template VMware Guest
  4. Look for value: Host memory usage in percents / vmware.vm.memory.usage

Result:
Values with over 100%

Expected:
The description of the item states: (https://www.zabbix.com/documentation/5.2/manual/config/items/itemtypes/simple_checks/vmware_keys)
Percentage of host physical memory that has been consumed.
So to my understanding, whatever the values does, it must be below 100% and never over.

 Comments   
Comment by Marco Hofmann [ 2021 Aug 23 ]

ping MVekslers who proposed the change and asestakovs who introduced the change in ZBXNEXT-6301

Comment by Michael Veksler [ 2021 Aug 25 ]

You are right. We should divide the value with type percent by 100.

Comment by Marco Hofmann [ 2021 Aug 25 ]

MVekslers May I ask politely, if there is the same issue with the following item keys:

vmware.hv.cpu.usage.perf && vmware.hv.cpu.utilization

See the following screenshot.

If yes, should I open another ZBX issue?

Comment by Michael Veksler [ 2021 Aug 25 ]

I have added list of metrics to description and I think we will fix all metrics together. Do not required to open additional ZBX

Comment by Marco Hofmann [ 2021 Aug 25 ]

Thank you very much, for the fast confirmation and communication. It was a pleasure, as always.

Comment by Michael Veksler [ 2021 Aug 31 ]

Available for testing in PR#2902

Comment by Michael Veksler [ 2021 Oct 01 ]

Available in:

Comment by Khatsayuk Alexander [ 2021 Oct 19 ]

MVekslers, look at an issue after upgrading to 5.4.6:

2308:20211018:225309.987 adding performance counter gpu/temperature[average]:559
2308:20211018:225309.987 Unknown performance counter 559 type of unitInfo:celsius
2308:20211018:225309.987 adding performance counter gpu/temperature[average,absolute]:559
2308:20211018:225309.987 Unknown performance counter 559 type of unitInfo:celsius

Comment by Michael Veksler [ 2021 Oct 19 ]

asand3r you are right. ZBX-20097

Comment by Oleksii Zagorskyi [ 2021 Oct 22 ]

Looks like there is one more new issue after this change - ZBX-20113

Generated at Tue Jan 07 21:56:35 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.