vSAN capacity disk performance metrics are missing in Aria Operations 8.18.0
search cancel

vSAN capacity disk performance metrics are missing in Aria Operations 8.18.0

book

Article ID: 398154

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

vSAN capacity disk performance metrics such as device latency, physical layer latency, physical layer throughput, physical layer IOPS, Guest latency, etc. are not available in Aria Operations 8.18.0.
 
vSAN capacity disk performance metrics are not collecting:
 
 
Review of the vSAN adapter logs revealed an error pattern, indicating an issue with querying Host disk mappings:
VsanStorageAdapter_xxxxx.log:
ERROR [vSAN Adapter Discovery Engine-pool-x-thread-xx] (#####) com.vmware.storage.helper.vimapi.VimApiImpl.getVsanVcHostDiskMapInfo - Exception while querying Host disk mapping for host host-#####
com.vmware.vim.binding.vim.fault.VsanFault: General vSAN error.
        at jdk.internal.reflect.GeneratedConstructorAccessor###.newInstance(Unknown Source) ~[?:?]
        at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ~[?:?]
        at java.lang.reflect.Constructor.newInstance(Unknown Source) ~[?:?]
        at java.lang.Class.newInstance(Unknown Source) ~[?:?]
        at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:xxx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.core.types.impl.DefaultDataObjectFactory.newDataObject(DefaultDataObjectFactory.java:xx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.ComplexStackContext.<init>(ComplexStackContext.java:xx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.parse(UnmarshallerImpl.java:xxx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl$UnmarshallSoapFaultContext.unmarshall(UnmarshallerImpl.java:xxx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:xx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.core.soap.impl.unmarshaller.UnmarshallerImpl.unmarshalSoapFault(UnmarshallerImpl.java:xx) ~[vlsiCore-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.SoapFaultStackContext.setValue(SoapFaultStackContext.java:xx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.processNextElement(ResponseUnmarshaller.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.ResponseUnmarshaller.unmarshal(ResponseUnmarshaller.java:xx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.unmarshalResponse(ResponseImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setResponse(ResponseImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.parseResponse(HttpExchangeBase.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:xx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:xxx) ~[vlsiClient-6.1.0.jar:?]
        at com.sun.proxy.$Proxy###.queryDiskMappings(Unknown Source) ~[?:?]
        at com.vmware.storage.helper.vimapi.VimApiImpl.getVsanVcHostDiskMapInfo(VimApiImpl.java:xxx) ~[storageAdaptersHelper.jar:?]
        at com.vmware.adapter3.vsan.objectloader.VsanDiskgroupLoader.discoverResources(VsanDiskgroupLoader.java:xxx) ~[VirtualAndPhysicalSANAdapter3.jar:?]
        at com.vmware.adapter3.vsan.objectloader.BaseObjectLoader.call(BaseObjectLoader.java:xx) ~[VirtualAndPhysicalSANAdapter3.jar:?]
        at com.vmware.adapter3.vsan.objectloader.BaseObjectLoader.call(BaseObjectLoader.java:xx) ~[VirtualAndPhysicalSANAdapter3.jar:?]
        at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
        at java.lang.Thread.run(Unknown Source) ~[?:?]
WARN  [vSAN Adapter Discovery Engine-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.objectloader.VsanDiskgroupLoader.discoverResources - Disk Mapping is null. Unable to process vSAN disk groups for host: xxx.xxx.xxx.xxx
WARN  [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.SpbmManager.getClusterProfilesIds - Fetched empty profile ids list
ERROR [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.SpbmManager.checkProfilesCompatibility - No profile id to check compatibility for
WARN  [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.SpbmManager.getProfiles - Null or empty list provided for getProfiles()
ERROR [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.handler.clusterprofiles.SpbmClusterProfilesHandler.getVsanProfileSpecs - Error while trying to get vSAN profiles by provided IDs
WARN  [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.SpbmManager.getClusterProfilesIds - Fetched empty profile ids list
ERROR [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.SpbmManager.checkProfilesCompatibility - No profile id to check compatibility for
WARN  [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.SpbmManager.getProfiles - Null or empty list provided for getProfiles()
ERROR [vSAN Cluster Metric Processing-pool-x-thread-x] (xxxxx) com.vmware.adapter3.vsan.spbm.handler.clusterprofiles.SpbmClusterProfilesHandler.getVsanProfileSpecs - Error while trying to get vSAN profiles by provided IDs

Environment

Aria Operations 8.18.1 or Older
ESXi 7.0.3 or Older
vSAN 7.0.3 or Older

Cause

Perf query calls were failing silently to retrieve Perf Metrics for ESXi hosts with version 7.0.x due to the use of MultiQueryMap to query for these Perf Metrics.

Resolution

Upgrade to a minimum of Aria Operations 8.18.2.
 
 
The fix for this issue is implemented in Aria Operations 8.18.2 and is also included in later versions.
 
vSAN capacity disk performance metrics are collecting:
 
Powered by Wolken Software