I have created three triggers using host items. The following are the expressions
Trigger 1:
1) {master:heapmem.nodata(240)}=1&{slave:heapmem.noda ta(240)}=1 -> this is to check data did come through in the past 240 secs
Trigger 2:
2) {master:heapmem.max(61,0)}=0 -> Check whether the heapmem is 0 in the past 61 secs
Trigger 3:
3) {slave:heapmem.max(61,0)}=0 -> Check whether the heapmem is 0 in the past 61 secs
For some reason the trigger #1 is getting enabled (triggered) even though the data is coming in every 60 seconds. I can see the data in the "latest data" in raw format and graphically. Any thoughts on why this is happening.
Even if trigger 1 is created without the & condition i.e. with only one expression say {master:heapmem.nodata(240)}=1, trigger events are getting generated even when data is received every 60 seconds.
The data is end to zabbix using zabbix_sender. Any reason for this behavior? Is there an issue with the trigger expression or is it a bug?
Trigger 1:
1) {master:heapmem.nodata(240)}=1&{slave:heapmem.noda ta(240)}=1 -> this is to check data did come through in the past 240 secs
Trigger 2:
2) {master:heapmem.max(61,0)}=0 -> Check whether the heapmem is 0 in the past 61 secs
Trigger 3:
3) {slave:heapmem.max(61,0)}=0 -> Check whether the heapmem is 0 in the past 61 secs
For some reason the trigger #1 is getting enabled (triggered) even though the data is coming in every 60 seconds. I can see the data in the "latest data" in raw format and graphically. Any thoughts on why this is happening.
Even if trigger 1 is created without the & condition i.e. with only one expression say {master:heapmem.nodata(240)}=1, trigger events are getting generated even when data is received every 60 seconds.
The data is end to zabbix using zabbix_sender. Any reason for this behavior? Is there an issue with the trigger expression or is it a bug?
Comment