ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarification on alarm fields


Article ID: 145410


Updated On:


NIMSOFT PROBES DX Unified Infrastructure Management (Nimsoft / UIM)


We have fetched alarms from Nimsoft through API connection. We require clarification on some of the fields present in the alarms.






Release : 9.1.0


- nas 9.x


<id>AR44426255-93781</id> # This is the NIMID which uniquely identifies an alarm.

<prevLevel>0</prevLevel> #This is the previous severity level of the alarm.

<alarmToken>as#system.cdm.avrg_total_cpu_above_err_threshold_proc</alarmToken> #(Optional) Defines the udata.token field in the alarm PDS, which sets the internationalization token for the alarm message. For more information on using the internationalization token, see Use a Localized Alarm in UMP->

<devId>D7D6587161617B677D9EBE62D03B9C977</devId> #This is the device ID for the alarm. A single device Id or comma-separated list of deviceIds against which to limit the alarms returned. A device Id will have the same syntax as: DCC87D8A5B58DE6268A9C178D490F9C96

<metId>ME44ED5A76E6C5E31E9B2B9B257B6D4FA</metId> #This is the metric ID for the alarm. The metric ID is the unique identifier for the metric that originated the alarm. Like the device ID, the metric ID is required to view the alarm in UMP and can be used to test pre-processing rules or Auto-Operators.