Problem with Proxy, nodata, and central zabbix server
Hi,
I've recently started having a problem with a few triggers. The triggers I have setup check a memory field whether it has data(using nodata) over the last 10 minutes. I use this to tell whether there is a problem with the zabbix client. It works perfectly for active check machines and machines sitting next to zabbix server(same subnet). But recently this trigger goes off a dozen times for each machine it's setup on(behind proxy) within a 15 minute period.
Is there something I need to set to ignore during the maintainance period or some trigger specific item to place in it? I'm kind of at a loss.
Rolandsym
I've recently started having a problem with a few triggers. The triggers I have setup check a memory field whether it has data(using nodata) over the last 10 minutes. I use this to tell whether there is a problem with the zabbix client. It works perfectly for active check machines and machines sitting next to zabbix server(same subnet). But recently this trigger goes off a dozen times for each machine it's setup on(behind proxy) within a 15 minute period.
- Machines connected via zabbix proxy.
- Trigger works correctly all other times.
- Happens every 23 hours(Housekeeping is set for 24) Which increases the hour of occurrence by 1 hour.
- Template used is also on machines on same subnet as zabbix primary
- No problem with other triggers
- Trigger goes off about 12 times per host and usually for 10 secs
- Trigger set for 600 seconds of no data.
- There is no gap on data received from host or particular item monitored by nodata.
- Zabbix 1.6.4 proxy and server.
Is there something I need to set to ignore during the maintainance period or some trigger specific item to place in it? I'm kind of at a loss.
Rolandsym