Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've recently installed Zabbix server on a VPS and am very happy with it. I've installed the client on appr. 6-7 other VPSs and everything works fine. The interface is smooth, and it produces some very nice graphs.
My only problem with the software is that I've set it up to send notifications on problems, but im receiving between 30 and 60 emails every day. Always something along "Server XXX is unreachable: PROBLEM", and a minute later: "Server XXX is unreachable: OK". Off course, Zabbix also recognizes when there are real problems, and e.g. when a server has been restarted. It just seems to me as if Zabbix very fast "gives up", or maybe times out faster than what suits my needs. I've been trying to google this problem several times, but given up, so now I'm trying this approach.

Does anyone know of how to adjust the fidelity of these notifications/triggers?

share|improve this question
are you using the default example templates ? if so, it most likely is the "status" item, which, actually is not suggested :) - you should change instead to to check host availability – Richlv Nov 3 '11 at 18:01
up vote 7 down vote accepted

I am using escalation functionality of Zabbix to suppress frequent On/Off messages. In general:

  • first messages trigger escalation chain, w/out emailing you
  • then, Zabbix waits for 5 mins (or whatever you set it up to) before sending a notification.
  • if in course of those 5 mins trigger state changes to off, you get NO notification and everything goes back to normal.
  • Nice part it that deshboard still shows


share|improve this answer
Thanks! That seems like what I was looking for. I adjusted the settings, and am now giving the system some time to see how the notification sending is affected. – anselmdk Nov 6 '11 at 17:12
After waiting patiently (and relaxing some web triggers), Zabbix emailing is finally working properly now. Thanks for the tip! – anselmdk Nov 30 '11 at 9:01

You can adjust the triggers as well. I've found the count() method handy.
Instead of triggering on last(0) try count(300,0,"eq")}>5 instead. This trigger an exception if the last 5 checks (assuming 60 seconds between checks) failed.

You can also disable the OK messages by adding the 'Trigger value = "PROBLEM"' condition. This change should be made in the actions configuration.

share|improve this answer
Actually, your count example will return the number of values in the last 300 seconds equal to 0. You then compare it to 5. The overall effect is to trigger an event if 5 or more "0" values occurred in the last 300 seconds. – G-Wiz Oct 24 '13 at 6:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.