Strange (incorrect?) behavior of template expression in event log

[dolfs]

I have created an alarm condition like this to raise: fabs([th0temp-age:999]-[thb0temp-age:999]) >= 100 (don't ask why), and the corresponding condition for clearing the alarm is: fabs([th0temp-age:999]-[thb0temp-age:999]) <= 3

When I go to the "Services" tab and hover over the orange "i" box I see that most recent evaluations. An example is attached.

Now during the interval covered by this log, the raise condition never is/becomes true, and the clear condition always is true. Yet, sometimes, there is a log line with the raise condition in it, evaluating to false. So the alarm is not actually raised, but the line should not appear, I think, and it surely does not appear every single time. So when is it supposed to appear. I would expect either every evaluation, or only when it evaluates to true.

That, I suspect, is a bug. It does not affect the functioning of the alarms, but makes looking at the log a little harder than strictly necessary.

[admin]

From the log I can see that raise condition is not as you said. I can see a second expression to be evaluated. Are you doing the brackets right? Please post the correct raise condition.

[dolfs]

The full raise condition:

Code: Select all

fabs([th0temp-age:999]-[thb0temp-age:999]) >= 100 && [mbsystem-lastgooddata] < 30

I simply left the second part out as it does not seem relevant, but there it is. The log shows that overall raise condition to evaluate to false.

[admin]

The idea of this log is to tell you about all evaluations done. Stripping unsuccessful raise or clear computations would contradict the idea to trouble shoot false formulated conditions.

[dolfs]

I understand that, but it does not seem to show all evaluations, or at least the raise condition is not evaluated as often as the clear condition. Why?