Hello,
Want to make sure the 5.4 upgrade will solve my VMware monitoring issues before I proceed. I'm currently using 5.0.2. Looks like the addition of the VMware FQDN template will fix the first issue, but I haven't found anything definitive on the second:
1st Issue: Problems & corresponding alerts/notifications for VMware guests (VMs) return the 'Host' value of the vCenter through which they are being monitored, as opposed to the actual VM.
2nd Issue: Based on the way discovery works in 5.0.2 using Template VM VMware, I can only define one Host group that isn't a Group prototype (i.e. 'Virtual machines' - see screenshot). Once all VMs are discovered and Host groups/Group prototypes are applied, it's impossible to add VMs to any other Host group.
The limitations become clear in even a modestly sized VMware environment; I'm monitoring one w/ thousands of VMs spread out across 20+ teams. Say Team Alpha has 50 Prod VMs in the environment and they only want to be alerted on disk space capacity. If you can't create a host group w/ the 50 VMs, how can you create an appropriate action? The only work around I can see isn't very good - in 'Conditions', choose 'Host' and add all 50 individual VMs. Very manual & time consuming.
Does 5.4 offer more flexibility on this front? Being able to apply new Host groups to discovered VMs is a must. Please include details if you've got this working in 5.4.
Thanks/Спасибо
Want to make sure the 5.4 upgrade will solve my VMware monitoring issues before I proceed. I'm currently using 5.0.2. Looks like the addition of the VMware FQDN template will fix the first issue, but I haven't found anything definitive on the second:
1st Issue: Problems & corresponding alerts/notifications for VMware guests (VMs) return the 'Host' value of the vCenter through which they are being monitored, as opposed to the actual VM.
2nd Issue: Based on the way discovery works in 5.0.2 using Template VM VMware, I can only define one Host group that isn't a Group prototype (i.e. 'Virtual machines' - see screenshot). Once all VMs are discovered and Host groups/Group prototypes are applied, it's impossible to add VMs to any other Host group.
The limitations become clear in even a modestly sized VMware environment; I'm monitoring one w/ thousands of VMs spread out across 20+ teams. Say Team Alpha has 50 Prod VMs in the environment and they only want to be alerted on disk space capacity. If you can't create a host group w/ the 50 VMs, how can you create an appropriate action? The only work around I can see isn't very good - in 'Conditions', choose 'Host' and add all 50 individual VMs. Very manual & time consuming.
Does 5.4 offer more flexibility on this front? Being able to apply new Host groups to discovered VMs is a must. Please include details if you've got this working in 5.4.
Thanks/Спасибо
Attached Files