Why all alerts generated by a MCS Enhanced profile are classified as "alarm" in the subsystem ID/info?

book

Article ID: 141664

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

We can see that that all alarms are classified as "Alarm" in subsystem info, when generated by a MCS enhanced profile:

This behavior doesn't happen when we configure a probe by using IM console, Admin Console or the "regular" MCS profiles.

Is this an expected behavior?

Example:

Let's consider two Linux servers. 

In one of them, we have configured MCS with setup_cdm and Memory_Monitor profiles.

The other one was configured with setup_cdm (enhanced) and Memory Monitor (enhanced) profiles.

The alarms of the first server  will appear classified as "Memory" in the subsystem info.

The alarms from the second server will appear classified as "Alarm" in the subsystem info.

Cause

If the plugin metric generated an alarm message, and it reached NAS, and if NAS did not find any subsystem id in the alarm message, then it converts that message subsystem to "alarm" by default. That's why we are able to see subsystem id as alarm in enhanced profiles alarms.

Environment

Release : 9.2.0

Component : UIM - MON_CONFIG_SERVICE

Resolution

This is a expected behavior.

Attachments