How to automatically disable trigger in few minutes

[kqfp31]

Hi
I configure item and trigger that alarm if host don't have connection by icmp protocol.
I have two triggers:
a) First with warning status, that alarm if host is unreacheble by 1 minute
b) Second with average status that alarm if host is unreacheble by 3 minute
How to modify first trigger that will be disable automatically by 3 minutes? Independently if the host is still unreachable.
Greatings.

[Yello]

Hi,
I suspect that disabling of triggers isn't what you need to in this instance. Can you explain in detail the behaviour you're trying to model please?


Regards,
David

[kqfp31]

Hi,
I suspect that disabling of triggers isn't what you need to in this instance. Can you explain in detail the behaviour you're trying to model please?


Regards,
David

I mean that I need to disable alarm from showing on dashboard. Even if this problem is still actual.
Probably, I have trigger that alarm on dashboard that disk is only 10% free. I want this alarm to display on dashboard only by few minutes. No matter If disk space was change.

[Yello]

I mean that I need to disable alarm from showing on dashboard. Even if this problem is still actual.
Probably, I have trigger that alarm on dashboard that disk is only 10% free. I want this alarm to display on dashboard only by few minutes. No matter If disk space was change.

Can you explain why you need this behaviour? If you don't provide the full picture then it won't be possible to offer a complete answer. In the absence of that I'll have a stab at it although what you're asking for sounds rather silly if truth be told.

Here's a suggestion that might get you moving in the right direction (pseudo-code):

{TRIGGER.VALUE = 0 & item.last > <thresh> & item.count(<trigger_num_samples>,<thresh>,"eq")=1} | {TRIGGER.VALUE = 1 & item.count(<suppress_num_samples>,<thresh>,"gt")=< suppress_num_samples>}

Key:
trigger_num_samples - sampling window in which there must not have been previous breaches of the threshold
suppress_num_samples - sampling windows in which all values must exceed the threshold
thresh - trigger threshold

Intended logic:
1. Trigger will fire if in an OK state and latest value is greater than the threshold and no other values over a lookback period have exceeded the threshold. This is so that the trigger cannot fire off data which had previously triggered a suppression.
2. Trigger will return to an ok state from a problem state if all values over a shorter window exceed the threshold.
3. Trigger will then stay in an ok state until condition 1 is met.

So this configuration will flip the trigger off and on periodically. The period will depend on the trigger configuration. All trigger can do is change state between OK, PROBLEM and UNKNOWN states. A trigger cannot disable itself or any other trigger for that matter.

Another approach might be to fire an action which calls an external script. This script will then find the trigger via the api and disable it if it has been in a problem state for more than x minutes. Why you would ever want to do that is beyond me. But that is an option too.


Regards,
David

[Yello]

BTW, please note that I am not actually working on a zabbix system at the moment so I don't have the opportunity to test any of this.