-
Type:
Problem report
-
Resolution: Fixed
-
Priority:
Major
-
Affects Version/s: 4.0.0beta2
-
Component/s: Frontend (F)
-
Sprint 43, Sprint 44
-
0.5
Steps to reproduce:
Create a rather complex trigger with very long expression.
This is used as example.
({TRIGGER.VALUE}=0 and
(((({Template Expression Test:log[test.log,test,,,skip].count(#10,ERROR,like)}/
({Template Expression Test:log[test.log,test,,,skip].count(#10,ERROR,like)}+
{Template Expression Test:log[test.log,test,,,skip].count(#10,PARSED,like)}))
*100)
+
(({Template Expression Test:log[test2.log,test,,,skip].count(#10,ERROR,like)}/
({Template Expression Test:log[test2.log,test,,,skip].count(#10,ERROR,like)}+
{Template Expression Test:log[test2.log,test,,,skip].count(#10,PARSED,like)}))
*100))/2)
>49)
or
({TRIGGER.VALUE}=1 and
(((({Template Expression Test:log[test.log,test,,,skip].count(#10,ERROR,like)}/
({Template Expression Test:log[test.log,test,,,skip].count(#10,ERROR,like)}+
{Template Expression Test:log[test.log,test,,,skip].count(#10,PARSED,like)}))
*100)
+
(({Template Expression Test:log[test2.log,test,,,skip].count(#10,ERROR,like)}/
({Template Expression Test:log[test2.log,test,,,skip].count(#10,ERROR,like)}+
{Template Expression Test:log[test2.log,test,,,skip].count(#10,PARSED,like)}))
*100))/2)
>0)
Open the Expression constructor and click Test
Result:
The long arithmetical parts of the trigger remain in a single line and the trigger evaluation result is not visible.
The evaluation results (TRUE, FALSE) are visible in the Inspect element section of the browser though.
Expected:
Trigger expression results displayed in some way.
Might be caused by this: ZBXNEXT-4127
