{TRIGGER.VALUE} is neither 1 nor 0

[Ruddimaster]

Zabbix 7.2.4., MySQL DB, Ubuntu 24.04 LTS

I can't say when I started having this problem. I guess after the upgrade to 7.2.

To avoid toggling, I often work with {TRIGGER.VALUE}.

Now I have the problem that

({TRIGGER.VALUE}=0 and last(/Server01/vfs.fs.size[D:,pfree])<10) or ({TRIGGER.VALUE}=1 and last(/Server01/vfs.fs.size[D:,pfree])<11)

no longer works.
The trigger is no longer activated under 10.

last(/Server01/vfs.fs.size[D:,pfree])<10)

works

This senseless trigger goes to PROBLEM, but should not:

({TRIGGER.VALUE}<>0 and {TRIGGER.VALUE}<>1 and last(/Server01/vfs.fs.size[D:,pfree])<10)

So apparently TRIGGER.VALUE is neither 1 nor 0.

Does anyone also have the same problem?

[cyber]

Recovery expressions. Keeping it open until it is low enough to not flap..

[Ruddimaster]

so I have done an other test:

({TRIGGER.VALUE}=0 or {TRIGGER.VALUE}=1) and last(/Server01/vfs.fs.size[D:,pfree])< 10

If the trigger.value is 1 or 0 the or-link must be always true. but it isn't . I have still 9% free space. an the trigger is still OK.

[Ruddimaster]

Has someone the same issue?

[Ruddimaster]

I also have this behavior with a fresh installed appliance
-> https://support.zabbix.com/browse/ZBX-26205

[Ruddimaster]

Does any know what PS-2379 means?
I can't see the actual status... I fearing that the Zabbix Development Team does not know that this important macro does not work?

[cyber]

Does any know what PS-2379 means?

Without context, it can be anything..

[Ruddimaster]

You will find the context at this URL https://support.zabbix.com/browse/ZBX-26205

[Ruddimaster]

Am I the only one who works with {TRIGGER.VALUE}, as this no longer works since 7.2?

[Ruddimaster]

No one use {TRIGGER.VALUE}?

[cyber]

TBH, not using it... But bug seems to be confirmed, pity, it is not worked on..

[Ruddimaster]

Thanks for you're response.

TBH, not using it...

How do you prevent this from happening when a value goes back and forth just at the limit of the threshold value?
In my environment the trigger memory and disk usage often toggle. To prevent this I use e.g.
({TRIGGER.VALUE}=0 and last(/Server01/vfs.fs.size[D:,pfree])<10) or ({TRIGGER.VALUE}=1 and last(/Server01/vfs.fs.size[D:,pfree])<11)

In Nagios/Icinga there was a built-in default setting called flap detection:
"https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/3/en/flapping.htm

At this blog there was an idea to rebuild this (from founder itself):
https://blog.zabbix.com/no-more-flap...mart-way/1488/

And now the developers are letting this issue lie for months

[cyber]

Recovery expressions. Keeping it open until it is low enough to not flap..

[Ruddimaster]

Thanks for this hint... it was hard work to change all my templates, but It works..