[ZBX-12094] After Upgrading vCSA to 6.5.0.5500 Average read latency and bytes received display Performance counter is not available Created: 2017 Apr 21  Updated: 2024 Apr 10  Resolved: 2018 Jun 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: 3.2.4
Fix Version/s: 4.0 (plan)

Type: Problem report Priority: Major
Reporter: Phillip Hernandez Assignee: Martins Valkovskis
Resolution: Fixed Votes: 1
Labels: templates, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos 7


Attachments: PNG File 2017-04-21_14-22-43.png    
Issue Links:
Duplicate
Team: Team D
Sprint: Sprint 33, Sprint 34, Sprint 35
Story Points: 0

 Description   

After upgrading to 6.5.0.5500 Build Number 5318154 Average read latency and bytes received are no longer available. I suspect Vmware has change the call in the API.

Are there any workarounds for this?



 Comments   
Comment by Érick Rangel Gomes [ 2017 Jun 19 ]

I have the same issue in 3.2.6 version, in a Linux Debian.
The items change frequently the status between Supported and Not supported, but just the items Latency and Bytes received and transmitted.

Comment by Sergejs Paskevics [ 2018 May 31 ]

Part of metrics no longer collected by default in 6.5 version.
You need to enable metrics via the vSphere.

This link will help you:
https://www.opvizor.com/vmware-vsphere-6-api-limitation-when-querying-performance-data-introduction/

Comment by Sergejs Paskevics [ 2018 May 31 ]

(1) [D] necessary to document, that part of metric can be disabled by default in vmware.

Added to the troubleshooting section. Please review. If OK, it could be copied to other versions. RESOLVED

martins-v Tried to make it more general. Please have a look.

s.paskevics CLOSED

Generated at Wed Apr 24 01:01:13 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.