Did anybody else notice the ~44 new and ~5 updated modules around VMware dropping in the last hour or so? Does anyone know how to implement these new modules? Since there was talk of making the instances into resources I don’t want to just bring them in without knowing how it’s going to mess with my device list (which is tightly bound to billing for us).
AdvisorPretty sure we’re not going to use it then since adding devices in is associated with billing and we don’t just add stuff in because it exists.
We’re probably in the same camp. I’m pretty sure that we get what we need in terms of host monitoring through vCenter. I can’t imagine that we would add the hosts individually into LM as there would be a cost associated with adding each host. We may just look at customising alerts on the existing datasources so that they take into account of host maintenance mode in the vCenter inventory (i.e. don’t throw an alert if a host is in maint mode).
Hi,
@Stuart Weenig . Migrating to the new modules will not convert instances into Resources. However, the Enhanced Script NetScan filters make it easy to add the ESXi hosts and Mission Critical VMs you want to monitor as Resources. You can setup filters that mirror your business logic and schedule the NetScan to query vCenter on (as frequent as) an hourly basis to add the exact resources you want, so what you deem to need monitoring gets monitored automatically.
So all the netscan really does is add the resources I already have in LM and create some group structure? Pretty sure we’re not going to use it then since adding devices in is associated with billing and we don’t just add stuff in because it exists. Is there a propertysource we can use to grab the additional properties the nestcan would set without all the stuff we don’t need?
Is there any benefit to importing the datasources if I’m not using the netscan?
That’s a huge netscan script and a lot of warnings about changing it. If you’re so worried about people changing it, why not make it a snippet and then the netscan script is 3-4 lines (import the snippet, run the snippet, output the data)?
Product ManagerWe’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,
To maintain historical data, make sure to disable previous datasources rather than changing the AppliesTo or deleting them.
Product ManagerDid anybody else notice the ~44 new and ~5 updated modules around VMware dropping in the last hour or so? Does anyone know how to implement these new modules? Since there was talk of making the instances into resources I don’t want to just bring them in without knowing how it’s going to mess with my device list (which is tightly bound to billing for us).
Hi,
Product ManagerThat would be interesting… one of our pain points at the moment is putting vSphere hosts into SDT. We don’t actually monitor the hosts as such at the moment, just through the vCenter, so the vCenter is the only resource. As I understand it, if our operations team wants to SDT a host, we’d have to do it under each datasource it appears in under it’s parent vCenter.
If hosts and datastores etc show up a devices that can be separately SDT’d then that’d be great.
Likewise, we’re setting up a separate LM instance to do stuff like this in!
Dave
To accomplish this with the new modules and onboarding process, you can have the Enhanced Script NetScan add your desired vSphere Clusters (ESXi hosts) as Resources and disable the following DataSources:
VMware_vCenter_HostPerformance
VMware_vCenter_HostVSwitch
VMware_vCenter_HostInterfaces
After doing this, you can selectively SDT by DataCenter, Cluster, Resource Pool, or individual ESXi host.
Product ManagerBelow are some highlights about the new VMware vSphere modules.
AdvisorThat would be interesting… one of our pain points at the moment is putting vSphere hosts into SDT. We don’t actually monitor the hosts as such at the moment, just through the vCenter, so the vCenter is the only resource. As I understand it, if our operations team wants to SDT a host, we’d have to do it under each datasource it appears in under it’s parent vCenter.
If hosts and datastores etc show up a devices that can be separately SDT’d then that’d be great.
Likewise, we’re setting up a separate LM instance to do stuff like this in!
Dave
Supposedly the new ones create resources instead of instances (not sure how that magic works), so that would allow you to do a soft migration maintaining the old stuff while getting the new stuff working.
If the QA on these modules matches the QA on the common configsources, these ain’t getting imported any time soon.