Has anyone else noticed that, when using a condition in the alarm template, the results are inverted when using the Greater Than / Less Than functions?
Server version – 10.0.8.0 – 9300
Client version – 10.0.2022.1608
I have the following configured in an alarm template with the corresponding results. Once applied, the alarms are generated inversely of what was expected (greater than / less than returning the opposite). Also, ‘not initialize’ seemed to alert for both rather than being ignored by both.
I believe it is because the condition is to not monitor the parameter on which it is applied when that condition is satisfied, as stated in the help. In other words, if the condition is true, the parameter won’t be monitored.
Hi Steve,
As Gelber indicated in his previous post, according to DataMiner Help (Using conditions in an alarm template), the parameter will not be monitored when the condition is satisfied.
Regarding the Not Initialized values, from DataMiner 10.0.7.0 onwards, conditions are supported that check whether a parameter value is equal or not equal to Not Initialized