Better triggers for Zabbix

[burner1024]

There are 2 issues with current triggers conditions:
1) They're subject to flapping. Using min()/max() or avg() instead of last() could be a solution.
2) They don't check if there's actually data received, so they're not reliable. nodata() trigger may be used to remedy that.

So, a sample trigger instead of
{Percona MySQL Server Template:MySQL.Threads-running.last(0)}>100
would be
{Percona MySQL Server Template:MySQL.Threads-running.min(300)}>100 | {Percona MySQL Server Template:MySQL.Threads-running.nodata(300)} = 1

[Roman Vynar (roman-vynar)]

An update interval for most of the items is 300 secs. So it looks like it doesn't matter what we use min(300) or last(0), they are equivalent in this case, right?
In order to make it efficient we need to decrease update interval to 1 min at least but it does not work well with the current php script re-used from Cacti templates, unfortunately.

[burner1024 (burner1024)]

That is correct. But we also can increase the averaging interval instead, of course.

[Roman Vynar (roman-vynar)]

Yes, but it's less chance to catch a problem if it's a short spike.

Ilya, did you implement those triggers on your servers and if you can share them?

[burner1024 (burner1024)]

Attached is my current configuration. Without it, I get emails continuously.
There's a post from Zabbix on this topic: http://blog.zabbix.com/no-more-flapping-define-triggers-the-smart-way/1488/. I always try to do at least 3 point averaging in triggers.

Yes, it would be better if actual script worked faster. But that's probably the scope of another ticket.