I've been using Zabbix for evaluation purposes for a couple of weeks now. In my opinion this is a great product, so keep up the good work.
I started running with version zabbix-1.1alpha10 and updated now to zabbix-1.1alpha11. There is a small issue with the str type trigger function. It's easier to explain with an example:
({foobar.foobar.com:checklog[smsgate].str(ERROR)}=1)&({foobar.foobar.com:checklog[smsgate].str(service group cannot be found)}#1)
The above trigger works so that the custom script checklog[] returns lines from a logfile and if there is an "ERROR" text in the line the first statement is true. The second statement is true only if "service group not found" is not found on the line. So this trigger is true if i get any other ERROR messages than "ERROR service group not found" kind of a message.
I can happily say that this works perfectly, but i have to manually put the "service group not found" text in the database in the parameter column in the funtions table. When creating str functions from the web GUI, the GUI only allows one word inside the str parameter. If i try to put in more than one word i get error: [ERROR:Invalid trigger expression]
Expression [{juusto.cubio.net:checklog[smsgate].str(service group cannot)}] does not match to [server:key.func(param)]
Below is an example what the GUI is capable of:
({foobar.foobar.com:checklog[smsgate].str(ERROR)}=1)&({foobar.foobar.com:checklog[smsgate].str(service)}#1)
So this would match to any ERROR messages that have "ERROR" and "service" words in it. This is a bit too broad matching for efective filtering of error messages.
It would make the product just a little bit better if str functions with many words could be added with the GUI.
Thx
I started running with version zabbix-1.1alpha10 and updated now to zabbix-1.1alpha11. There is a small issue with the str type trigger function. It's easier to explain with an example:
({foobar.foobar.com:checklog[smsgate].str(ERROR)}=1)&({foobar.foobar.com:checklog[smsgate].str(service group cannot be found)}#1)
The above trigger works so that the custom script checklog[] returns lines from a logfile and if there is an "ERROR" text in the line the first statement is true. The second statement is true only if "service group not found" is not found on the line. So this trigger is true if i get any other ERROR messages than "ERROR service group not found" kind of a message.
I can happily say that this works perfectly, but i have to manually put the "service group not found" text in the database in the parameter column in the funtions table. When creating str functions from the web GUI, the GUI only allows one word inside the str parameter. If i try to put in more than one word i get error: [ERROR:Invalid trigger expression]
Expression [{juusto.cubio.net:checklog[smsgate].str(service group cannot)}] does not match to [server:key.func(param)]
Below is an example what the GUI is capable of:
({foobar.foobar.com:checklog[smsgate].str(ERROR)}=1)&({foobar.foobar.com:checklog[smsgate].str(service)}#1)
So this would match to any ERROR messages that have "ERROR" and "service" words in it. This is a bit too broad matching for efective filtering of error messages.
It would make the product just a little bit better if str functions with many words could be added with the GUI.
Thx