Triggers Visualization in Overview

[existenz]

Hello!

I'm doing a migration from Zabbix 1.8.6 to 3.0.9 and have some issues with visualization of trigger in Overview screen.

For example, I create triggers in version 1.8.6 and their names are the same (CPU load on {HOSTNAME} > limit), though Expressions are different ({SRV1:system.cpu.util[].last(0)}>50 - first threshold, {SRV1:system.cpu.util[].last(0)}>90 - second threshold), then in Overview there will be only one string with this trigger, and different thresholds will color the green field with red/yellow.

In version 3.0.9 it doesn't work. In Overview there is each trigger, they are not combined any more, like in 1.8.6 version. So if I would like to have 10 thresholds, it would be 10 triggers shown in Overview, while in 1.8.6 it would be only one. It's not convenient at all.

Is it a bug or a feature? Is it configurable behavior?

Thank you in advance!

[existenz]

Basically it looks like images attached.

In 1.8.6 it is 4 triggers (same name), but different expressions.
In Overview we can see only one trigger shown (4 triggers combined to one)

In 3.0.6 four triggers with the same name are not combined in Overview screen, we can see 4 different triggers. The same for Test trigger.

The goal is to show only one trigger in Overview, not 4. (or 2 for Test trigger).

Is it possible?

[batchenr]

Basically it looks like images attached.

In 1.8.6 it is 4 triggers (same name), but different expressions.
In Overview we can see only one trigger shown (4 triggers combined to one)

In 3.0.6 four triggers with the same name are not combined in Overview screen, we can see 4 different triggers. The same for Test trigger.

The goal is to show only one trigger in Overview, not 4. (or 2 for Test trigger).

Is it possible?

you need to make your trigger with some limit - for exsample
if you want an warning trigger to alert when its <6 and and
it to change to disaster when its <9 then make this triggers :

last.()}<6 and last.()}>9
and the disaster trigger
last.()}<9 and last.()}>10

or the values that you want and then the trigger will change and u will never have 4 triggers.

full exsample :
({servername:itemkey.last()}<6) and
({servername:itemkey.last()}>9)

[existenz]

Thank you for your answer, batchenr, but still it doesn't work as expected.

I'll try to explain one more time.

For example we have a host, and monitoring CPU load on it. This host has three triggers

First trigger
Name: CPU load on {HOSTNAME} > limit
Expression: {SRV1:system.cpu.util[].last(0)}>50} notifies for warning (yellow color on overview)

Second trigger
Name: CPU load on {HOSTNAME} > limit (!same as first one!)
Expression: {SRV1:system.cpu.util[].last(0)}>75} notifies for high (orange color on overview)

Third trigger
Name: CPU load on {HOSTNAME} > limit (!same as first one and second one!)
Expression: {SRV1:system.cpu.util[].last(0)}>90} notifies for disaster (red color on overview)

These triggers are working correctly on both versions of Zabbix.

But in overview in Zabbix 1.8.6 there is only ONE string with these three triggers combined into one.
In Zabbix 3.0.9 there are THREE strings (not joined)



Of course I did make triggers with more detailed thresholds, like you advised, but it doesn't change the picture in overview, there are still a lot of triggers compared to 1.8.6 version.



Am I still doing something wrong?

[batchenr]

Thank you for your answer, batchenr, but still it doesn't work as expected.

I'll try to explain one more time.

For example we have a host, and monitoring CPU load on it. This host has three triggers

First trigger
Name: CPU load on {HOSTNAME} > limit
Expression: {SRV1:system.cpu.util[].last(0)}>50} notifies for warning (yellow color on overview)

Second trigger
Name: CPU load on {HOSTNAME} > limit (!same as first one!)
Expression: {SRV1:system.cpu.util[].last(0)}>75} notifies for high (orange color on overview)

Third trigger
Name: CPU load on {HOSTNAME} > limit (!same as first one and second one!)
Expression: {SRV1:system.cpu.util[].last(0)}>90} notifies for disaster (red color on overview)

These triggers are working correctly on both versions of Zabbix.

But in overview in Zabbix 1.8.6 there is only ONE string with these three triggers combined into one.
In Zabbix 3.0.9 there are THREE strings (not joined)



Of course I did make triggers with more detailed thresholds, like you advised, but it doesn't change the picture in overview, there are still a lot of triggers compared to 1.8.6 version.



Am I still doing something wrong?

i have same kind of trigger - look you set it like :

Name: CPU load on {HOSTNAME} > limit (!same as first one!)
Expression: {SRV1:system.cpu.util[].last(0)}>75} notifies for high (orange color on overview)

my trigger looks like that :

({deadpool.office.dev:system.run["/home/zabbix/balance_check.sh "].last()}<17000) and
({deadpool.office.dev:system.run["/home/zabbix/balance_check.sh "].last()}>13000)

try making last(0) to last()

[wyang]

We are using 2.4, with which only one trigger shows in overview when the dependencies between triggers with different thresholds on a same metric are defined.

Does it mean the trigger dependency not working in release 3.x?