-
Problem report
-
Resolution: Fixed
-
Blocker
-
3.2.7rc1
-
Zabbix 3.2.7rc1 (revision 68572)
-
Sprint 9, Sprint 10, Sprint 11, Sprint 12, Sprint 13, Sprint 14, Sprint 15, Sprint 16, Sprint 17, Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 23
-
5
Hello, team.
I am observing very strange Zabbix behavior: for random amount of my 480000 items and 430000 triggers new values aren't triggering problem\ok trigger state change - if trigger got into Problem some time ago, new incoming value X = 0 for example with min(X)<1 won't switch trigger to Ok state.
Situation can be fixed by going into item on host and clearing history\trends for it.
One of the examples can be seen in attached screenshots. I'll be happy to give any kind of diagnostic information. Also I'll check generic 3.2.6 to see if bug repeats here.
- depends on
-
ZBXNEXT-3006 A cache to provide multiple metrics of a single custom function
- Closed
- is duplicated by
-
ZBX-10462 Trigger status stuck
- Closed
-
ZBX-11768 "cannot find open problem events for triggerid" message appears in zabbix_server.log after upgrade to 3.2.2
- Closed
-
ZBX-13776 Zabbix 3.4.4 doesn't resolve triggers
- Closed
-
ZBX-12859 False "More than 100 items having missing data for more than 10 minutes" alert
- Closed
- part of
-
ZBX-12179 Database errors can go unnoticed with DBselect(), DBfetch() functions
- Confirmed