What VMAN looks at is the hypervisor thin provisioning and not the storage hardware thin provisioning. I'm not familiar with the HP StoreVirtual but does it's settings take precedence over how VMWare is configured? Virtualization manager is only going to know what the VMware API is telling it.
Apologies Chris, I should have specified. We're a Hyper-V 2012 shop, no VMware. I know a majority of VMan's capabilities are only applicable to VMware and not Hyper-V because it's more established and the API is more broad and available. I do not use Solarwinds Storage Manager since the HP StoreVirtual console does the same thing very well so I just use VMan to report stats on the Hyper-V and VM performance and such. I wonder why v6.1.x saw no issues with our Hypervisors in regards to datastore overallocation but v6.2.x does. We're severely under-provisioned so I feel like this is a false positive.