Forum Discussion
Taking a quick peak at a sampling the latest vmware datasource code in Exchange. It looks like:
- VMware_ESXi_* looks at esx only
- VMware_vSphere looks at vcenter first, then vcsa, then esx
- VMware_vCenterAppliance_* looks at vcsa first, then vcenter, then esx
- VMware_vCenter_* looks at vcenter first, then vcsa, then esx
I didn’t really test these, but I would make sure you have the latest Vmware PropertySources and DataSources.
Had a deeper dig in to the docs at VMware vSphere Monitoring | LogicMonitor:
vCenter Server Appliance Host Properties
Property | Value | Required |
vcenter.user | vCenter read-only user | Yes |
vcenter.pass | vCenter read-only password | Yes |
Note: For backwards compatibility with older generations of vCenter modules, if the credentials are not set, the follwoing vCenter User Properties are used. However, it is recommended to use the preceding vCenter Server Appliance Host Properties vcenter prefix when configuring devices.
vCenter User Properties
Property | Value |
vcsa.user | vCenter read-only user |
vcsa.pass | vCenter read-only password |
esx.user | vCenter read-only user |
esx.pass | vCenter read-only password |
Neither vcenter.* or vcsa.* seem to work work for me when esx.* is also present (unless as above I override esx.user directly on the resource). If I remove esx.* and leave just vcenter.* (or vcsa.*) at the parent for inheritence, vCenter works but ESX host do not.
Related Content
- 10 months ago
- 3 months ago