Str() trigger expression not working as expected

[StealthJoe]

Lets say I have an item that will return either true or false and the history is something like this:

true
true
true
true
false
true
true

And I have a trigger expression like the below:

{Zabbix Agent:CheckStatus.str(true)}=0

I will get a problem created when the "false" value is returned but when the next item comes in as "true" the problem does not resolve. In fact, it never resolves even after repeated "true" values. I fixed one of them by adding a recovery expression but if the text can return more than one value this may not work.

Is this to be expected? From what the Zabbix Wiki says str() should only evaluate the last value. Should I just switch to using count() instead?

My Zabbix Server is 4.2.8.

[dimir]

Yes, since you are using only one parameter to str() it will always evaluate the latest value. Your expression looks correct and the problem should resolve after receiving "true" value. Could you show the configuration of your trigger, especially these options:

[StealthJoe]

Yes, since you are using only one parameter to str() it will always evaluate the latest value. Your expression looks correct and the problem should resolve after receiving "true" value. Could you show the configuration of your trigger, especially these options:

Here is the trigger in question. I did remove some personal information as this is a custom user parameter item but otherwise the configuration is the same.

[dimir]

Looks good. How often is your configuration reloaded by the server (option CacheUpdateFrequency in zabbix_server.conf)?

[StealthJoe]

Looks good. How often is your configuration reloaded by the server (option CacheUpdateFrequency in zabbix_server.conf)?

It is set to the default which looks to be 60s?

[dimir]

Could you show the values coming to this item after the trigger changed to PROBLEM?

[StealthJoe]

Could you show the values coming to this item after the trigger changed to PROBLEM?

Here is an example from a UserParameter item. The trigger in this case would be:

{Zabbix Agent:CheckStatus.str(Good)}=0

I should note that this (and most of my text items) are set to "Discard unchanged with heartbeat" using pre-processing.

 [TABLE]
[TR]
[/TR]
[TR]
[TD]2020-08-17 19:02:17[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-17 12:36:32[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 22:26:55[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 22:24:52[/TD]
 			[TD]Bad[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 22:16:36[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 22:15:34[/TD]
 			[TD]Bad[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 19:05:34[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 19:04:33[/TD]
 			[TD]Bad[/TD]
 		[/TR]
[TR]
[TD]2020-08-14 18:13:32[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-13 14:31:10[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-12 12:02:52[/TD]
 			[TD]Good[/TD]
 		[/TR]
[TR]
[TD]2020-08-12 12:00:48[/TD]
 			[TD]Bad[/TD]
 		[/TR]
[/TABLE]

[dimir]

I should note that this (and most of my text items) are set to "Discard unchanged with heartbeat" using pre-processing.

Oh, that makes sense. So you will need to wait till heartbeat is reached or send "Bad" and then "Good" again. The "unchanged" values are discarded without reaching to trigger processing.

[StealthJoe]

Oh, that makes sense. So you will need to wait till heartbeat is reached or send "Bad" and then "Good" again. The "unchanged" values are discarded without reaching to trigger processing.

If you see in the example the heartbeat is reached which is why there are multiple "Good" values in a row. Shouldn't these values be processed?

[dimir]

Of course they should. And the trigger should resolve to OK.