2.2 - hypervisor monitoring

[mrogers-9898]

Hey All,

Can someone point me in the right direction to setting up vmware esx monitoring with 2.2?

All I've been able to find is the item values from the 2.2 manual - https://www.zabbix.com/documentation...ks/vmware_keys

I'm sure there is more to it. How is the host portion configured, do I need macros for that URL, do I need to authenticate somehow?

[tchjts1]

If you wish for Zabbix to autodiscover your hypervisors, as well as the VM's attached, then set up the (ESX) host as you normally would, but configure your macros as per the below screenshot, and then assign Template Virt VMware to that ESX host. Note that your URL macro must end with /sdk

Whatever user you use, must have at least read rights to gain access to the ESX URL

I would suggest doing this in a test environment before doing it in production.

If you don't want it to discover all your VM's, then skip adding the above mentioned template and I guess you would just attach the Template Virt VMware Hypervisor template.

[mrogers-9898]

Thanks, that's a good tip.

I've done this, but I'm getting not-supported.

Does it with with ESXi?

Again; does anyone have a link to the reference manual/instructions for this part of the config?

Is it possible to check using zabbix_get? I'll have to authenticate somehow first wont I?

[euska]

I've got the same problem. Any idea ?

[mrogers-9898]

this is all I could find - https://www.zabbix.com/documentation.../vm_monitoring

but it did bring me find the problems with my testing, I modified the supplied template's items - where they had the macro {HOST.HOST} I changed that to my own host macro of {$UUID} and populated that with the right value which I got from http://kb.vmware.com/selfservice/mic...rnalId=1006250

[francescoRo]

Hi mrogers-9898,

can you explain exactly all the steps you did?
I put the macro {$UUID} in the host side, but I did not understand what you did with the template.

Thank in advance.

[budiman]

Same problem here...

Same problem here. I'hv been googling but cannot find step by step tutorial to implement this. Do we need to install something like zabbix agent on the hypervisor or just configure on zabbix front end and let zabbix discover the VM itself?

[mrogers-9898]

Hi guys,

Sorry I never got this working, I couldn't find any proper documentation on it.

[gleepwurp]

Hi Guys,

I do have Vmware monitoring going on my systems here.

I'll try to help out as I can...

1st, you don't need any kind of Zabbix agent on your ESX infrastructure. You just need to have a vCenter account that has at least read access to your vCenter Console.

ok, so first, you create an "Host" for your hypervisor in Zabbix, and assign it the "Template Virt VMware". This template contains a discovery rule for discovering VMs in your vCenter. However, in order for that discovery rule to work, you need to create the following user macros in your Hypervisor "host" in zabbix (like tchjts1 mentioned in post #2 of this thread). It is used by the discovery process to know where to find your Hypervisor, and how to log in:

{$URL} --> Your vCenter URL (http://<some_location>/sdk
{$USERNAME} --> Your "read" username account on vCenter
{$PASSWORD} --> Your "read" password

Once that is set, and your hypervisor "Zabbix" host is created, the discovery process should kick over and start adding VMWare devices in Zabbix. Might take some time to get started.

HTH,

G.

[budiman]

Hi Guys,

I do have Vmware monitoring going on my systems here.

I'll try to help out as I can...

1st, you don't need any kind of Zabbix agent on your ESX infrastructure. You just need to have a vCenter account that has at least read access to your vCenter Console.

ok, so first, you create an "Host" for your hypervisor in Zabbix, and assign it the "Template Virt VMware". This template contains a discovery rule for discovering VMs in your vCenter. However, in order for that discovery rule to work, you need to create the following user macros in your Hypervisor "host" in zabbix (like tchjts1 mentioned in post #2 of this thread). It is used by the discovery process to know where to find your Hypervisor, and how to log in:

{$URL} --> Your vCenter URL (http://<some_location>/sdk
{$USERNAME} --> Your "read" username account on vCenter
{$PASSWORD} --> Your "read" password

Once that is set, and your hypervisor "Zabbix" host is created, the discovery process should kick over and start adding VMWare devices in Zabbix. Might take some time to get started.

HTH,

G.

Ohh.. I See... I have 4 VM ESXi 4.1 but without vCenter Server. Usually I just use vsphere client to manage my VM. I have tried to use my host vm ip address as {$URL}, but zabbix still cannot discover my VM.

Thank you very much for your help.

[budiman]

Eurekaaa....

Ohh.. I See... I have 4 VM ESXi 4.1 but without vCenter Server. Usually I just use vsphere client to manage my VM. I have tried to use my host vm ip address as {$URL}, but zabbix still cannot discover my VM.

Thank you very much for your help.

Hi all.. I have solved the problem. After I read carefully from the documentation, I missed one part that we must set the StartVMwareCollectors option in Zabbix server configuration file (/etc/zabbix/zabbix_server.conf) to 1 or more. After I edit the configuration file and wait for a moment depending on discovery rule interval values, suddenly there are many host groups named "Discover VMware VMs". I hope this can help.

[tatapoum]

You can also check VmBix (https://github.com/dav3860/vmbix) for an alternate way to monitor your VMs and hypervisors.

[ikarogabriel]

Just to complement, you have to activate the managed object browser. At least in EXSI version 6.5, it is disabled by default. It only worked here after I activated it.

[mulbzh]

Just to complement, you have to activate the managed object browser. At least in EXSI version 6.5, it is disabled by default. It only worked here after I activated it.

I use ESXI 6.5
i activated Config.HostAgent.plugins.solo.enableMob , that it ?

after, i add my host, and added {$PASSWORD}, {$URL}, {$USERNAME}
what URL did you put ? just https://IP ?

after this, i added StartVMwareCollectors=5 in zabbix_server.conf and restarted zabbix

for the moment, i see Nothing :-(

[SBO]

what URL did you put ? just https://IP

Mm. Wondering what the problem can be..

Note that your URL macro must end with /sdk

{$URL} --> Your vCenter URL (http://<some_location>/sdk