Action Repeats

[knarfling]

I seem to be having some trouble with action repeats. I have a server that is pretty hammered (replacing it soon), and every so often, the processor load triggers as too high, and I get a page. This part is working fine. However, even after the processor load is back down below alert levels, I get repeated pages.

So I guess my question is on how repeats work. I want to get repeat pages if the problem is not fixed, but I don't want to keep getting pages after the problem is fixed. Should I disable repeats and create a second trigger that is time based to handle escalation?

[James Wells]

Greetings,

I want to get repeat pages if the problem is not fixed, but I don't want to keep getting pages after the problem is fixed.

Most likely you have the alert set to send out whether the trigger is true or false. What you want to do is go back into your alert and make sure it only sends when the trigger is true. This way, you will get the repeats, only when the trigger has been tripped, but not when it is reset.

[knarfling]

Trigger Value

No, one of the conditions is Trigger Value = ON. I check the web page and it the events section shows the value going to ON and then to OFF. The Action pages shows only one email sent, but I received 3 of them, 10 minutes apart. (My repeats were configured as 3 at 600 seconds).

[peter_field]

This is happening on my system also

knarfling is talking about setting the "Repeat" option on the action to "Repeat", and then setting the number of repeats to be sent. This is different to the action conditions, and I imagine a practical use for this is if you have a very urgent trigger, you can have it nag you every 10minutes or whatever you set the delay to.

I have noticed this same behaviour. Once the trigger is tripped, it will send the number of repeats set on the action, regardless of the state of the trigger. For example, I set the repeats to 10, 1 hour apart, a trigger went ON and then OFF within the next minute, and I was still getting emails 10 hours later saying the trigger was ON.

[bbrendon]

Repeats still broke.

Is this behavior a bug or a feature? I thought repeats were broke in early 1.1 but its 1.1.6 now, and I'm not sure how they are supposed to work. Seems to me if the trigger status=FALSE, then repeats should STOP. I would imagine repeats should also stop if you acknowledge the trigger.

The documentation says:

Repeat = Send repeat messages. ZABBIX stops sending repeated messages if the trigger changes its status

Sounds like a BUG. Because I have no active triggers and I'm still getting a zillion emails because I enabled repeats.

[bbrendon]

Further analysis suggests this might be working, though I may have still found a bug.

2007.Feb.24 14:52:41	Network error on server1	ON 	High
2007.Feb.24 14:52:41	Network error on server1	OFF 	High

ON is listed at the top of the list and the time of the ON/OFF is the same which I think is causing the repeats even though it is really OFF.

Also, acknowledging a trigger does not disable repeats. Can I request that this be enabled?

[James Wells]

Also, acknowledging a trigger does not disable repeats. Can I request that this be enabled?

This feature does not exist in the mainline Zabbix build, nor is it currently on the roadmap, however, I have posted a patch which includes this feature. You can find the patch in PATCH: Multiple fixes against 1.1.5 Follow the instructions for altering the table schema, then apply the patch for 1.1.6