Server Tagging

[Himanshu Agrawal]

We want to tag some cloud servers so that MOM(Managers of Managers) layer can filter out these servers.

So we have written "cloud" in  controller->advance->origin section (tagging in User Tag1 and User Tag2 didn't work)

When we have generated a test alarm, then MOM layer is getting "cloud" in the agent host field, which we want.

But when robot actually goes inactive, then alert it is showing it original hostname i.e. name of the hub in hostname field in their console.

Why is it so? 

[David Michel]

It is the hub and not the robot that reports the robot as inactive. Logic followed is the robot can't report itself as down, when it is down. This tech doc provides some info on the robot inactive alarm.

What is the cause of an Alarm if a server robot go - CA Knowledge 

 

As you found out the User Tags added to the controller settings is only for that robot. Most likely a nas auto operator pre-processing rule or profile can take out these alarms, add the user tag, and then repost it back to the bus.