I am trying to create a custom group that contains all the vSwitch0 vSwitches, but only if they have a port group called "XYZ".
The group membership criterias seem to allow to check from the perspective of the switch only (if it's a child of something, has a specific parent etc...).
It works if I do the other way around (port groups named XYZ with parents of vSwitch0), but that returns the list of port groups not switches.
Any insight would be much appreciated.
This is to exclude certain symptoms/alerts for vSwitch0 that have iSCSI port groups defined on them...
Thanks for your time!
As far as i know vROps supports objects, metrics, relationships for vDS only and not for vSS,
You have a link somewhere to back this up? Doesn't make much sense to be honest, especially when the objects exist...
This link contains all the metrics and properties for vROps objects. Only distributed switches are mentioned, no standard switches.
Metric, Property, and Alert Definitions
I also checked this in a production environment and i could not find anything related to standard switches. Standard switches is not a collectable object in vROps.
I don't know the reason why this is not available in vROps.
Maybe sunnydua201110141 or jddias can provide more clarity about this.
What I don't understand is that when I create the rule as per the screenshot above, the ESXvSwitch object exists, shows me all the vswitch0 in the environment, same for the port groups.