Better triggers for Zabbix
Bug #1327197 reported by
burner1024
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Monitoring Plugins |
Triaged
|
Medium
|
Unassigned |
Bug Description
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:
would be
{Percona MySQL Server Template:
tags: | added: zabbix |
Changed in percona-monitoring-plugins: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
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.