Am working with zabbix 3.0 enabling virtualization metrics for the first time. Followed the instructions setting up the macros, and have collection working ok for discovered VMs and for explicit VMs if I set the Host name on the host configuration to the UUID, then the built-in keys in the Template Virt VmWare Guest template for HOST.HOST work for most items. But get no data for cpu ready.
In my particular case I don't want to use discovery; have a zabbix server for a small subset of all the VMs administered by the vCenter and desire creating explicitly the hosts. I've found that if I change {$HOST.HOST} to {$UUID} in the metric item key, it can work for most virtualization metrics if I explicitly create a $UUID macro setting it to the specific UUID for the VM. But again, I get no data for cpu ready. My key looks like this: vmware.vm.cpu.ready[{$URL},{$UUID}]
I've tried all kinds of varieties of UUID, #UUID, VM.UUID, $UUID and can see no reason why the above fails to get any data when
vmware.vm.cpu.usage[{$URL},{$UUID}]
works fine.
I can see cpu ready from the vsphere client on the vCenter, and I can see it using vmbix. But I'd like to eliminate having to have a separate vmbix instance running and get it from the out of the box zabbix server. What am I missing?
A somewhat related question: why does discovery show different UUID for zabbix host than the UUIDs I see from vmbix going to the same vCenter with a 'zabbix_get -s vplab089 -p 12050 -k vmbix.vm.discovery[*]' call? Isn't the UUID coming from the vCenter independent of who's asking for it?
In my particular case I don't want to use discovery; have a zabbix server for a small subset of all the VMs administered by the vCenter and desire creating explicitly the hosts. I've found that if I change {$HOST.HOST} to {$UUID} in the metric item key, it can work for most virtualization metrics if I explicitly create a $UUID macro setting it to the specific UUID for the VM. But again, I get no data for cpu ready. My key looks like this: vmware.vm.cpu.ready[{$URL},{$UUID}]
I've tried all kinds of varieties of UUID, #UUID, VM.UUID, $UUID and can see no reason why the above fails to get any data when
vmware.vm.cpu.usage[{$URL},{$UUID}]
works fine.
I can see cpu ready from the vsphere client on the vCenter, and I can see it using vmbix. But I'd like to eliminate having to have a separate vmbix instance running and get it from the out of the box zabbix server. What am I missing?
A somewhat related question: why does discovery show different UUID for zabbix host than the UUIDs I see from vmbix going to the same vCenter with a 'zabbix_get -s vplab089 -p 12050 -k vmbix.vm.discovery[*]' call? Isn't the UUID coming from the vCenter independent of who's asking for it?
Comment