About Tags

The Cloud Services Portal Infoblox Platform provides tags that you use to identify and group objects. A tag is a label that consists of a key and associated value(s) that you define when you create the tag. Tags are useful when you want to categorize objects by specific purposes, such as by location, so you can easily identify them based on the tags you assign to them.

When you create an object, such as an on-prem hosta NIOS-X server, you can define the tag key and associated value(s) for the object, so you can easily locate the object in the future. For example, you can create a tag key called "Location" with a value of "London, UK" when you create an on-prem hosta NIOS-X server, so you can specify its location. You can then use the same "Location = London, UK" tag for other objects that share the same attribute. This is useful when you want to identify all the on-prem hosts and networks that are in London, UK. All you need to do is filter or search using the tag key = "Location" and the value = "London, UK" after you have assigned the tag to the relevant objects.

When updating an existing tag of restricted type with a different set of allowed values, then this change will not be reflected on existing mapping of other objects (e.g., NIOS-X Servers, Join Tokens, Schedule Software Updates, DNS, etc.). User have to make the same changes to existing mapping of other objects

Best Practices for Using Tags

The following are best practices for using tags: 

• You can create multiple tags for various purposes and assign them to objects that you want to group, so you can define and track them in a systematic way. Infoblox recommends that you devise a set of tags that meets the needs and requirements for specific purposes. Using a consistent set of tag keys makes managing your objects more effective.

• Tags are not automatically assigned to any objects. When you create an object, you can define a tag or tags for the object. Once you create a tag, the key and value are stored in the system, and you can assign the same tag to other objects, if applicable.

• In situations where you need to modify the tag key or tag value(s) for a specific object, you essentially introduce a new tag (if it does not already exist) to the system. The original tag key and value(s) still exist, and your modifications do not affect the objects to which you have assigned the original tag.

• When

  updating an

  updating an existing tag

  key

  of restricted type with a different set of allowed values,

  there is no impact

  then this change will not be reflected on existing mapping of other objects (e.g.,

  hosts, join tokens, deferral schedules, dns configurations

  NIOS-X Servers, Join Tokens, Schedule Software Updates, DNS, etc.). Organizations must make the same changes to existing mapping of other objects

• When you remove a tag from an object, you are removing the association of the tag from the object. 

• When you revoke a tag from the system, the tag will automatically be removed from the associated objects.

• When you revoke a tag from the system, its revocation will affect the tags being used by other objects. 

• When necessary, you can reactivate a tag after you have revoked it. When you reactivate a revoked tag, the tag will associate with the objects that they were previously associated wtih.

For information about how to create and apply tags, see the following: