mark.j wrote:
vC Ops can't alert on 100% of the potential conditions that vCenter actions can be configured for. The criteria for defining alerts differs between vC Ops and vCenter. vCenter has the leg-up on interpreting certain events (non-condition) alerts, however OOTB vC Ops can interpret some. If you can identify any that are not interpreted, you can add them to the Faults/events config file on the VMware adapter (see /conf and the VMware adapter manual)). If you can make it work with vC Ops, though, I would do it and avoid the extended vCenter action configuration.
Mark J
I'm not exactly sure what you mean by "vCenter has the leg-up on interpreting certain events (non-condition) alerts, however OOTB vC Ops can interpret some. If you can identify any that are not interpreted ..." specifically the "interpreting certain events (non-condition) alerts" part.
What is a non-condition event? By "not interpreted" does that mean -- vCOPs has the event/condition information, but simply has no decode for it (sort of like WireShark not having a decode for some odd protocol)?