USM not changing status icon for devices when a alarm is created using UIMAPI

[Carlos Hugo Martin Carranza Olivera]

We are creating alarms using UIMAPI. Following the KB "Alarm source change in Logmon to the correct DEV_ID" (https://knowledge.broadcom.com/external/article?articleId=4677) we get the alarm to appear on a previously created device also using the UIMAPI.
The problem we have now is that the device status icon does not change depending on the severity of the alarm and when reviewing the alarm in the database, we notice that the alarm is missing the met_id. We have tried to enter this field manually, but the result is the same.
Some will know what can be done?
El JSON of the alarm is:
{
"level":"5",
"message":"Test Message",
"severity":"Critical",
"source":"wuim201",
"suppressionKey":"DiskUsageRobot",
"level":"5",
"visible":true,
"custom1":"A custom property 1",
"custom2":"A custom property 2",
"custom3":"A custom property 3",
"custom4":"A custom property 4",
"custom5":"A custom property 5"
}

[Gene Howard]

What version of UIM, ump and UIMAPI are you using?



------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Gene Howard]

so from the example you can see the following:
{
"id": "string",
"level": 0,
"severity": "string",
"message": "string",
"prevLevel": 0,
"hostname": "string",
"source": "string",
"timeOrigin": "2020-05-21T14:21:35.188Z",
"timeArrival": "2020-05-21T14:21:35.188Z",
"timeLast": "2020-05-21T14:21:35.188Z",
"subsystem": "string",
"prevSubsystem": "string",
"subsystemId": "string",
"domain": "string",
"hub": "string",
"robot": "string",
"nas": "string",
"probe": "string",
"origin": "string",
"suppressionKey": "string",
"suppressionCount": 0,
"assignedTo": "string",
"assignedBy": "string",
"timeAssigned": "2020-05-21T14:21:35.188Z",
"userTag1": "string",
"userTag2": "string",
"visible": false,
"custom1": "string",
"custom2": "string",
"custom3": "string",
"custom4": "string",
"custom5": "string",
"alarmToken": "string",
"devId": "string",
"metId": "string",
"ciType": "string",
"ciName": "string",
"variables": [
{
"name": "string",
"type": "string",
"description": "string",
"status": 0,
"value": "string"
}
]
}

You have to fill in all for of these with valid information for the alarm to work and show in USM correctly

------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------

[Carlos Hugo Martin Carranza Olivera]

Gene,
Thanks for the replay.
Can you tell me where I can get those values?

[Franklin Ravi D'souza]

Hi 

Can explore query in below KB to get the values

How to determine correct Metric Type information in the Top N report or Group Trend Report for UMP

https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=15533

[Carlos Hugo Martin Carranza Olivera]

Franklin,
Thanks for your answer.
I have tested alarm generation with the following JSON:
{
"level 5",
"message": "Device alarm test message 20200526 1800",
"severity": "Critical",
"suppressionKey": "ApiTestAlarma",
"visible": true,
"source": "plcaecoapp1_vmware",
"devId": "DBA2210DC430F39DA99F4D0A66F85402E",
"metId": "MB3B3E5542BC47F1355180766BE2EA47E",
"ciType": "1.3",
"ciName": "nimbus"
}
But the dev_id was replaced by that of the UMP.