"User Tag 1" field different in alarm and alarm_update queue

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

There are around 200 MS SQL servers where we have installed Windows robot and have updated the "User Tag 1" field to "DB_Server".

We have created two queues, one is "alarm" queue and other is "alarm update" queue. These queues are used by the Moogsoft tool which pulls alarm data from these queues which then processes the alarms and sends it to a ticketing tool.

Issue is the user tag field in alarm queue is coming as "user_tag_1" but in the alarm_update queue it is coming as "user_tag1" which is causing issue.  Could you please help us understand why this user tag 1 field is coming different in both queues.

Environment

• Release: 20.4

Resolution

Please follow the Moogsoft Integration documentation.

https://docs.moogsoft.com/Enterprise.8.0.0/en/uim-configuration.html 

https://docs.moogsoft.com/Enterprise.8.0.0/en/configure-the-ca-uim-lam.html

The user tags are working as designed.

One way to workaround this issue youre experiencing with the user tag header/udata would be to:

Use a NAS Auto-Operator profile(s) to repost the specific alarms you want to be sent to Moogsoft, to a different, unique message Subject, e.g., 'moogsoft_alarms' and the Moogsoft queue could subscribe to this message Subject.

This should circumvent the issue youre experiencing with different user tag syntaxes ("user_tag_1" versus "user_tag1")