top of page

vSphere Tags and Custom Attributes in VCF Operations

  • Writer: Brock Peterson
    Brock Peterson
  • 3 hours ago
  • 2 min read

We've discussed vSphere Tags and Custom Attributes a couple times before:


Both are very powerful, yet quite different in terms of how they present in VCF Operations. Let's have a look, all screenshots here are taken from VCF Operations 9.0.2.



Here is a VM in my lab with both Tags and Custom Attributes on it. Over in VCF Operations, they look like this.



The Properties themselves look like this.



You'll notice the vSphere Custom Attributes show under Summary - Custom Tags and show as their key:value pair. However, the vSphere Tags which show under Summary - vSphere tag, concatenate both tags together into a string. This is why I prefer using Custom Attributes to vSphere Tags. For example, if you're using these VM Properties in a View, they'll look like this.


As you can see the vSphere Custom Attributes show quite nicely because they are presented in key:value pairs. Whereas the vSphere Tag is just a long string of Tags.


Now, if you're creating VCF Operations Custom Groups based on vSphere Tags or Custom Attributes you have another option.



You could use the VM Properties to define your Custom Group, but here you'll notice there is an addition option in our dropdown called Tag. This represents the vSphere Tags on the VM as shown on the Summary Page and here.



These aren't usable in Views, but they are usable in Custom Groups, which can come in handy if you're filtering on vSphere Tag key:value pairs, especially multiple. For example, here I'm create a Custom Group of VMs based on two vSphere Tags.



Which gives me the VMs I wanted.



These are the five VMs in my lab with vSphere Tags on them.



So, as you can see there are ways you can use both vSphere Tags and Custom Attributes in VCF Operations, I prefer vSphere Custom Attributes because they are consistently presented in key:value format. I hope this was helpful, enjoy!

Comments


    bottom of page