Hi to all,
we have problems with 1.3.6 and triggers. There are still unknown triggers, even if we cleaned up db (history*, trends). We thought it is due to our database that it is slow. But now we know it is not due to database. Data for triggers are OK, when I look into latest values, I see right dates, times and values.
Please, how evaluation if trigger works? When and how it is evaluated?
If there is trapper item, trigger is evaluated only when next data are sent or continously from history?
Some of triggers which are still unknown:
Pocitac A406-1 mimo provoz A406-1:errstate.str(OK)=0
Host consuelo down consuelo:icmpping.max(#4)=0
WEB (HTTP) server is down on consuelo consuelo:http.last(0)<1
I think it is only in simple checks and trapper items.
Next, when I will drop ALL icmp traffic to zabbix server, all triggers are showing state "ON" which is good. When I enable icmp pings again, after some time there is unknown state..
Thanx!
we have problems with 1.3.6 and triggers. There are still unknown triggers, even if we cleaned up db (history*, trends). We thought it is due to our database that it is slow. But now we know it is not due to database. Data for triggers are OK, when I look into latest values, I see right dates, times and values.
Please, how evaluation if trigger works? When and how it is evaluated?
If there is trapper item, trigger is evaluated only when next data are sent or continously from history?
Some of triggers which are still unknown:
Pocitac A406-1 mimo provoz A406-1:errstate.str(OK)=0
Host consuelo down consuelo:icmpping.max(#4)=0
WEB (HTTP) server is down on consuelo consuelo:http.last(0)<1
I think it is only in simple checks and trapper items.
Next, when I will drop ALL icmp traffic to zabbix server, all triggers are showing state "ON" which is good. When I enable icmp pings again, after some time there is unknown state..
Thanx!
Comment