Hi all,
To start, I've been trying to get a full blown Zabbix environment off the ground for about three years, since I first heard about it. I had one partially running, but it fell victim to an unexpected hard drive failure (is there any other kind?).
In 2.2, I REALLY like the concept of being able to just plug in the info for my VMware ESXi boxes and get stats for all the VMs running on them. Unfortunately, I'm not quite getting all the info I'd like (graphs, etc.), and I feel like I'd be further along by just deploying the agent to each VM. This would also let me group all the VMs in a more meaningful way. I'm also one of those weird folks who's running ESXi on Apple hardware so I can virtualize OS X.
Does anyone else have any anecdotal reasoning for using VMware discovery instead of Zabbix agents on each VM?
Thanks!
Pete
To start, I've been trying to get a full blown Zabbix environment off the ground for about three years, since I first heard about it. I had one partially running, but it fell victim to an unexpected hard drive failure (is there any other kind?).
In 2.2, I REALLY like the concept of being able to just plug in the info for my VMware ESXi boxes and get stats for all the VMs running on them. Unfortunately, I'm not quite getting all the info I'd like (graphs, etc.), and I feel like I'd be further along by just deploying the agent to each VM. This would also let me group all the VMs in a more meaningful way. I'm also one of those weird folks who's running ESXi on Apple hardware so I can virtualize OS X.

Does anyone else have any anecdotal reasoning for using VMware discovery instead of Zabbix agents on each VM?
Thanks!
Pete
Comment