Hi,
We would like to generate port link state alarms for wich the severity depends on an extra parameter that is updated on the fly by an automation script.
The parameter used in the condition has the following values: Mon-Wa, Mon-Mi, Mon-Ma, Mon-C.
In the example we describe here the parameter has the value Mon-C, which should create a critical alarm for a port that has a link status not equal to 'Up'.
Each condition maps on the corresponding severity.
This seems to work fine during several actions (update 'Port Monitored' param via automation/manual, restart element, ...).
Only if we update/apply the alarm template the severity of the alarm falls back to 'Warning' and is set to 'Critical' after a couple of seconds.
The question is how this conditional monitoring should work with multiple lines?
I believe that we're looking at some unexpected behavior here, but someone can correct me if I'm wrong.
Some context:
Having looked at the setup with Tom, I can confirm that there are two different apparent behaviors for two distinct situations.
You could say that the behavior for the "disable" state of the condition differs between normal operations and after alarm template application.
For normal operation, the "disable" is treated as though the line would not be present in the alarm template in the first place. i.e. DataMiner will iterate from top to bottom, ignoring every line that matches the condition.
In short, a disable here, behaves rather as removal of the line from the alarm template. This is not as we expect, as Miguel's response indicated. We expect that with a single filter, only the top statement would be evaluated. If it's disabled, it's parsed as disabled within the alarm console.
However, after alarm template application, Tom gets a Warning alarm for about 12 seconds, before the alarm severity flips to Critical.
This is a distinctly different behavior. It seems to imply two things:
1. Conditional monitoring didn't trigger, because the top line would not allow a line with "warning" state column to be alarmed
2. The expected behavior does occur here, and the top line is evaluated.
The question here remains then, if the expected behavior is that conditional monitoring should fully eliminate a line from the alarm template (= what is disabled) and thus work with 4 identical indexes and thusly, if the warning state after an alarm template change is a bug?