21 Jun 2023 05:15 PM - last edited on 22 Jun 2023 08:11 AM by MaciejNeumann
The VCenter Name entity currently exists in the selector, but we are currently unable to use this to generate tags.
The ESXI cluster/host names are not consistent enough to be used comprehensively, the VCenter Name is really the only property that will allow us to determine support team ownership for accurate distribution of generated alerts to responsible teams. Until this is resolved comprehensive alerting will not be possible.
Support case 180985 was created for this problem.
Solved! Go to Solution.
28 Jun 2023 06:37 PM
VMWare Name property visible above. It appears the data is there, just not indexed in a way that allows for application of tags based on the property.
01 Aug 2023 08:39 PM
Only available solution is to create Manual tags based on ESXI host name (hardcoded) and use that tag to setup Management zones based on VCenter.
01 Aug 2023 09:07 PM - edited 01 Aug 2023 09:08 PM
Hi @nethier. You can create auto-tags based on Entity Selector if you want to tag the VCenter just use:
type(VCENTER),detectedName("XXXXXXX")
01 Aug 2023 09:10 PM
Also you can do more complex selections like:
type(HYPERVISOR),toRelationships.manages(type(VCENTER),detectedName("YYYYYYYYYY"))
01 Aug 2023 09:30 PM
@svedulaLet me understand what are you trying to achieve.
20 Jun 2024 07:47 PM
Hi @DanielS , Sorry this was posted some time ago but just seeing it now.
What you have posted above is exactly that I'm looking for.
Ability to include in MZ, Type VCenter should support auto tagging, and ideally if we could edit those tags from the screen cap location that you show that would be ideal too. Currently the selector values still don't allow tag assignment to the VCenter type - we would like to auto-propagate tags down to ESXI Clusters, Hosts, Guests, Services, etc. from the top VCenter level.
10 Apr 2024 10:59 PM
Move this idea to general QA because is possible to do it with the Entity Selector.