Here's a problem I've noticed in most Zabbix (1.1bx) versions I've run so far; when a number of triggers occur at the same time, the email for every single trigger isn't send out.
Here's how I noticed;
I have a number of linux machines and logging on to every single one and recompiling Zabbix whenever we get a version bump takes a lot of time. This and a few other simular tasks are best done by scripts remotely executed through ssh. So after an afternoon of scripting, I can update every Zabbix installation on every (linux) server. Today I upgraded to 1.1beta7 and within an hour, it was compiled on all linux hosts. Zabbix monitors the agent version and checks it's status every 30 minutes. You can imagine I get about 10 to 15 triggers at once when I do a version bump this way. But I only receive an email for 2 or 3 of those triggers. I definately want the other mails too. In this case, it's something I know and caused myself, but if a router fails and a dozen hosts become unreachable, I want to know about it, even if I don't have my tr_status.php page within view.
Here's how I noticed;
I have a number of linux machines and logging on to every single one and recompiling Zabbix whenever we get a version bump takes a lot of time. This and a few other simular tasks are best done by scripts remotely executed through ssh. So after an afternoon of scripting, I can update every Zabbix installation on every (linux) server. Today I upgraded to 1.1beta7 and within an hour, it was compiled on all linux hosts. Zabbix monitors the agent version and checks it's status every 30 minutes. You can imagine I get about 10 to 15 triggers at once when I do a version bump this way. But I only receive an email for 2 or 3 of those triggers. I definately want the other mails too. In this case, it's something I know and caused myself, but if a router fails and a dozen hosts become unreachable, I want to know about it, even if I don't have my tr_status.php page within view.


Comment