What I mean is a trigger like so:
{PHY_LINUX_STD:vfs.fs.size[/,pused].count(300, 90, "gt")}>1
Basically, if the fs usage is above 90% for more than one sample over 5 minutes, trip the trigger. But, looking at the zabbix debug log, it appears the "gt" operator isn't implemented.
19315:20080124:220443 ItemId:19483 Evaluating count(300, 90, "gt")
19315:20080124:220443 In evaluate_function(count)
19315:20080124:220443 In evaluate_COUNT(param:300, 90, "gt")
19315:20080124:220443 Query [select count(value) from history_str where clock>1201229983 and value like '90' and itemid=19483] 19315:20080124:220443 End evaluate_COUNT
19315:20080124:220443 End of evaluate_function(result:0)
As well, vfs.fs.size[/,pused] is defined as a float. So the history_str table has no samples for it:
mysql> select count(*) from history_str where itemid=19483;
+----------+
| count(*) |
+----------+
| 0 |
+----------+
1 row in set (0.00 sec)
Instead they appear to be in the history table:
mysql> select count(*) from history where itemid=19483;
+----------+
| count(*) |
+----------+
| 5649 |
+----------+
1 row in set (0.01 sec)
I can still get my desired trigger via other means, just wanted to post this to see if this behavior isn't exactly correct.
Thanks,
Jeremy
{PHY_LINUX_STD:vfs.fs.size[/,pused].count(300, 90, "gt")}>1
Basically, if the fs usage is above 90% for more than one sample over 5 minutes, trip the trigger. But, looking at the zabbix debug log, it appears the "gt" operator isn't implemented.
19315:20080124:220443 ItemId:19483 Evaluating count(300, 90, "gt")
19315:20080124:220443 In evaluate_function(count)
19315:20080124:220443 In evaluate_COUNT(param:300, 90, "gt")
19315:20080124:220443 Query [select count(value) from history_str where clock>1201229983 and value like '90' and itemid=19483] 19315:20080124:220443 End evaluate_COUNT
19315:20080124:220443 End of evaluate_function(result:0)
As well, vfs.fs.size[/,pused] is defined as a float. So the history_str table has no samples for it:
mysql> select count(*) from history_str where itemid=19483;
+----------+
| count(*) |
+----------+
| 0 |
+----------+
1 row in set (0.00 sec)
Instead they appear to be in the history table:
mysql> select count(*) from history where itemid=19483;
+----------+
| count(*) |
+----------+
| 5649 |
+----------+
1 row in set (0.01 sec)
I can still get my desired trigger via other means, just wanted to post this to see if this behavior isn't exactly correct.
Thanks,
Jeremy
Comment