[ZBXNEXT-7131] Parse hardware sensors value for VMware monitoring Created: 2021 Dec 17 Updated: 2024 Apr 10 Resolved: 2022 Jun 02 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Proxy (P), Server (S), Templates (T) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Medium |
Reporter: | Sacha Zufferey | Assignee: | Michael Veksler |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
VMware |
Attachments: |
![]() ![]() |
||||||||||||
Issue Links: |
|
||||||||||||
Team: |
Description |
In complement of ZBXNEXT-6608, it could be interesting to recover the counters of the sensors. For example the number of ECC errors of a memory DIMM. Available in the vSphere Client via host > Monitoring > Hardware Health > Sensors If I'm right, the values come from the CIM Server / IPMI. |
Comments |
Comment by Sacha Zufferey [ 2021 Dec 22 ] |
Hi, Some additional information if it help, reading the sensor from different tools : Sensor : DDR4_P1_B2_ECC ================== UCS Server Statistics (From UCS Manager) ================== Name 1 min 15 min 15 min History 1 Hour 1 Hour History 1 Day 1 Day History 1 Week 1 Week History 2 Week 2 Week History Memory 5 (B2) error-stats DramWriteDataCorrectableCRCErrors 0 0 0 0 0 0 0 0 0 0 0 DramWriteDataUnCorrectableCRCErrors 0 0 0 0 0 0 0 0 0 0 0 AddressParityErrors 0 0 0 0 0 0 0 0 0 0 0 AddressParityErrorsCorrectable 0 0 0 0 0 0 0 0 0 0 0 AddressParityErrorsUnCorrectable 0 0 0 0 0 0 0 0 0 0 0 EccMultibitErrors 0 0 0 0 0 0 0 0 0 0 0 EccSinglebitErrors 0 0 0 0 1 4 8 13 0 13 0 MismatchErrors 0 0 0 0 0 0 0 0 0 0 0 ================== SEL LOGS (From UCS Manager) ================== CIMC | Memory DDR4_P1_B2_ECC #0x87 | read 2 correctable ECC errors on CPU1 DIMM B2 | Asserted CIMC | Memory DDR4_P1_B2_ECC #0x87 | read 1 correctable ECC errors on CPU1 DIMM B2 | Asserted ================== Zabbix Sensors (From vmware.hv.sensors.get) ================== { "@type": "HostNumericSensorInfo", "name": "Memory Module 4 DDR4_P1_B2_ECC", "healthState": { "label": "Green", "summary": "Sensor is operating under normal conditions", "key": "green" } , "currentReading": "0", "unitModifier": "-2", "baseUnits": "error", "rateUnits": "none", "sensorType": "memory" }, ================== VMware Sensors (From vSphere Client -> Monitor -> Hardware Health -> Sensors) ================== <CIM_NumericSensor key="0.8.4.135"> <Name>Memory Module 4 DDR4_P1_B2_ECC</Name> <HealthState>5</HealthState> <CurrentReading>0</CurrentReading> <UnitModifier>-2</UnitModifier> <BaseUnits/> <RateUnits>0</RateUnits> <ElementName>Memory Module 4 DDR4_P1_B2_ECC</ElementName> </CIM_NumericSensor> ================== UCS IPMI Tool (From ESXi SSH Command "/opt/ucs_tool_esxi/ucs_ipmitool sensor list") ================== DDR4_P1_B2_ECC | 250.000 | error | ok | na | na | na | na | na | 60250.000 |
Comment by Michael Veksler [ 2022 Mar 17 ] |
Is this information available through the VirtualCenter interface? Please take a screenshot. |
Comment by Sacha Zufferey [ 2022 Mar 18 ] |
Hi Michael,
Yes, it's available through : "Select the host in vCenter" > Monitor > Hardware Health > Sensors
Here is the screenshot.
|
Comment by Michael Veksler [ 2022 Mar 18 ] |
Hi sachazufferey, Thanks, I found all sensors, but their accessibility depends on the configuration of each HV. |
Comment by Sacha Zufferey [ 2022 Mar 18 ] |
Hi Michael, Indeed, a manufacturer-specific VIB is required... It could be complicated to process... |
Comment by Michael Veksler [ 2022 Jun 02 ] |
Implemented as part of
Documentation updated: |