We’re part the way through onboarding a load of internal and customer VMware platform platforms into LM, so interested in this as well.
I’d be interested to understand the reason for releasing new modules over updating the existing? The commit history for the brand new ones mentioned ‘optimized for vSphere 8’ but the AppliesTo doesn’t seem to limit them to vSphere 8 vCenters/hosts, so loathed to import them just yet as I expect we’ll have a lot of duplication in data collection and alerts if we did.
Dave
Hi, @Dave Lee. Because the new VMware_vSphere* and VMware_vCenterAppliance* modules communicate with vCenter (via API), we recommend following your change control process for migrations rather than running the previous and new modules in parallel (which could put an unnecessary burden on vCenter).
To maintain historical data, make sure to disable previous datasources rather than changing the AppliesTo or deleting them.