Repeating action after item changes value

[WhoWeAre]

Hi

I'm using Zabbix Server v5.4.1 and I was wondering whether there is an opportunity to send message (repeating trigger action) with new item value

What I mean:
I have an item which sums up amount of some processes on host. The trigger fires if this amount is higher than 5.
So
When this number reaches 6 I recieve the message, the trigger's fired, everything's fine.
If this value goes higher and reaches 8 e.g. I'll be able to see it in "Latest data" section, but won't get message about it, which is my goal
I've tried multiple "PROBLEM event generation mode", but it's not exactly what I'm looking for: it generates new problem after every check, no matter what item value is. While I wish to have one problem and recieve new messages only in case item value has changed.

[Hamardaban]

you may try multiple event generation mode with another one condition in trigger like (your.condition and (last.value > prev.value))

[Markku]

Usually that kind of cases are handled by creating multiple triggers (with different thresholds) and configuring dependency between them. I'm using that for example with temperature monitoring: first I get a warning, but if the temperature keeps rising, I'll get another problem with higher severity, and the previous problem kind of disappears at the same time.

Markku

[WhoWeAre]

Talking about my example - do you mean creating triggers for like >5, >10, >15 processes and so on?
Actually, there's escalation option which'll probably do the thing with sending message with newest data without creating new trigger (however, I wish it was data-related, not date :^) ). Gotta test both of the options

Anyway, thanks for your idea

[Markku]

Yeah, there is no option to escalate based on the value changing so dependent triggers are used for that.

Markku

[Hamardaban]

you may try multiple event generation mode with another one condition in trigger like (your.condition and (last.value > prev.value))

[WhoWeAre]

Wow, quite simple and effective. However, that idea never came to my mind. Thanks a lot - gotta try it with separate trigger. Main idea is to avoid numerous recovery messages, so I guess I'm gonna just create trigger with > rule and set no recovery actions for him
Many thanks - that one's gonna do the thing for me

[WhoWeAre]

Well, it works fine but generates three messages instead of one. Still no idea, why it happens