NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

Active IQ Unified Manager Discussions

"Hit-All-the-unspecific-Alarm-Rule" and escape for previous alarms?

mgruber
3,864 Views

Hi!

We are still running a OCUM5.1, yes update follow in the next days, but what am I seeking for is a solution for a problem which I think should be quite simple, but I didnt get it.

We have several Alarm, like "full volume", "*_latency",.... and so on, followed by some sort of "hit-all-the-rest-alarm". the intention is, the dedicated alarms should be mailed to some group of people, but the "hit-the-unspecific"-rule to another.

What is this "hit-the-unspecific"-Rule, simply: "Event: ALL; Severity: Error or worse; Group: global", now we are getting all alarms twice, the specific and the unspecific, cause the severity hits, I understand why that happens, BUT, is there any solution to get around that, or a escape-rule would be nice....if a specific alarm was triggered no other alarm is engaged.... or is the only solution to define alarms for every Event-Type to route that mailing?

I could work with groups, but the global-group would hit always...

cheers

Matthias

2 REPLIES 2

arunchak
3,864 Views

HI Gruber,

AFAIK, once you create an Alarm with "Event: ALL; Severity: Error or worse; Group: global", there is no way to exclude specific alarms form that list.

You could create separate alarms for every event-type to route the mailing.

Thanks,

  Arun

mgruber
3,865 Views

Hi!

Well, that is what I nearly expected, I had a small hope, that I have missed something or there is some sort of "hidden trick" 🙂

cheers

Matthias

Public