Hi All!
I have a little problem with the alarm key associated to alarm creation/generation: the effect of the problem is that the alarm browser don't show all the ("real") alarms actually active.
I try to explain the problem with a little example:
In the alarm Processing policy, for service problems I have the following two rules:
for "SERVICE_DOWN" event generate an alarm with alarm key "SERVICE_DOWN_%i" and send an email
for "SERVICE_UP" event resolve the alarm with key "SERVICE_DOWN_%i" and send an email
Suppose than on node X, I have two service with name "A" and "B".
Suppose that on node X the following event happens(in temporally order):
1)Service A goes down -> netxms create an alarm with key SERVICE_DOWN_IDNODEX
2)Service B goes down -> netxms create an alarm with key SERVICE_DOWN_IDNODEX -> The alarm key is equal to the alarm key of alarm 1, so alarm 2 overwrites alarm1!
3)Service B goes up -> netxms resolve alarms with SERVICE_DOWN_IDNODEX
In this case, the service A is down but no alarms is showed on Alarm Viewer!(Netxms do his job correctly)
Mail notification work correctly of course.
**)
I want to fix the situation changing the alarm key generation to:
SERVICE_DOWN -> create alarm with key "SERVICE_DOWN_%i_%5"
SERVICE_UP -> resolve alarm wth key "SERVICE_DOWN_%i_%3"
The %5 and %3, in alarm creation and alarm resolving respectively, provide the unique id of the dci.
Unfortunately, i have this problem for many events and many rules, and i can't test all of it.
So my question is, can i do the changes at point **) and be sure that alarm generation continue to works correctly?Are there some event for which macros %5 and %3 don't works?
I know that answer can be obvious, but i have to be sure that mail notification continue to works!
There is the hazard that a problem in the creation of alarm key cause problem to alarm creation and mail notification?
Thank You to All!