Idea Details

Current tagging does not extend beyond robots need API enhanced to tag non-robot configuration item

Last activity 12-19-2016 09:23 AM
Alquin's profile image
09-19-2016 11:23 AM

Situation:

The current tagging mechanism in CA Unified Infrastructure Management does not extend to devices that do not have robots installed locally. The user_tag1 and user_tag2 fields are a great why to create dynamic groups in Unified Service Management relating configuration items to services or applications. There is no way to tag devices that do not have robots.

 

Request:

As a UIM user or administrator (implied ACL requirement) I want the ability (in all languages supported by the product) to view, add, modify, or delete tags on devices and configuration items (both programmatically and through the product UI), and allow (all) product grouping capability access to those tags for the purposes of filtering items to populate a group manually or to group items dynamically based on tag values.

 

Why:

This is required so that we can show in alarms and in USM what is impacted visually allowing the NOC to focus on the top tier business application / service alarms before the lower tier ones.

 

The real request is to make tagging in UIM as easy as tagging this idea.


Comments

09-22-2016 12:37 PM

This behavior is an artifact of the product history. UserTag_1 and UserTag_2 are and always have been, attributes of the Robot. They are not, nor were ever intended to be used as attributes of a device.

 

Perhaps a more generalized request:

 

As a UIM user or administrator (implied ACL requirement) I want the ability (in all languages supported by the product) to add, modify, or delete tags on devices and configuration items (both programmatically and through the product UI), and allow (all) product grouping capability access to those tags for the purposes of filtering items to populate a group manually or to group items dynamically based on tag values.