Hello ...
it seems there is some "inconsistence" in SNMP polling in version 1.8.4.
I use SNMP for polling router and switch uptime, and created a trigger like {Uptime.change(0)}>1 .. to alert me when a device is rebooting.
after upgrade from 1.8.4rc2 to 1.8.4 I received tons of alerts. After looking at the last 500 values, I saw:
2011-03-18 11:11:39 1300457499 13707
2011-03-18 11:10:38 1300457438 13646
2011-03-18 11:09:40 1300457380 13588
2011-03-18 11:09:40 1300457380 13588
2011-03-18 11:08:41 1300457321 13529
2011-03-18 11:08:39 1300457319 13527
2011-03-18 11:07:42 1300457262 13470
2011-03-18 11:07:41 1300457261 13469
2011-03-18 11:06:41 1300457201 13409
it seems that even configured for a 60 second interval, he checks 2x a minuto.. sometimes the same second, sometimes 2 seconds later..
when the last value is the same as the previous, the trigger fires.
shutting down zabbix_server 1.8.4 and starting-up the saved 1.8.4RC2 version ... and all works like expected.
2011-03-18 11:36:41 1300459001 15209
2011-03-18 11:35:40 1300458940 15148
2011-03-18 11:34:39 1300458879 15087
2011-03-18 11:33:38 1300458818 15026
2011-03-18 11:32:42 1300458762 14970
2011-03-18 11:31:39 1300458699 14907
2011-03-18 11:30:40 1300458640 14848
2011-03-18 11:29:38 1300458578 14786
one check / minute.
Any ideas ?
Thanks
Franz
it seems there is some "inconsistence" in SNMP polling in version 1.8.4.
I use SNMP for polling router and switch uptime, and created a trigger like {Uptime.change(0)}>1 .. to alert me when a device is rebooting.
after upgrade from 1.8.4rc2 to 1.8.4 I received tons of alerts. After looking at the last 500 values, I saw:
2011-03-18 11:11:39 1300457499 13707
2011-03-18 11:10:38 1300457438 13646
2011-03-18 11:09:40 1300457380 13588
2011-03-18 11:09:40 1300457380 13588
2011-03-18 11:08:41 1300457321 13529
2011-03-18 11:08:39 1300457319 13527
2011-03-18 11:07:42 1300457262 13470
2011-03-18 11:07:41 1300457261 13469
2011-03-18 11:06:41 1300457201 13409
it seems that even configured for a 60 second interval, he checks 2x a minuto.. sometimes the same second, sometimes 2 seconds later..
when the last value is the same as the previous, the trigger fires.
shutting down zabbix_server 1.8.4 and starting-up the saved 1.8.4RC2 version ... and all works like expected.
2011-03-18 11:36:41 1300459001 15209
2011-03-18 11:35:40 1300458940 15148
2011-03-18 11:34:39 1300458879 15087
2011-03-18 11:33:38 1300458818 15026
2011-03-18 11:32:42 1300458762 14970
2011-03-18 11:31:39 1300458699 14907
2011-03-18 11:30:40 1300458640 14848
2011-03-18 11:29:38 1300458578 14786
one check / minute.
Any ideas ?
Thanks
Franz

Comment