-
Type:
Incident report
-
Resolution: Cannot Reproduce
-
Priority:
Major
-
None
-
Affects Version/s: 3.0.1
-
Component/s: Server (S)
-
None
-
Environment:Linux 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 06:09:11 CST 2016 x86_64 x86_64 x86_64 GNU/Linux
zabbix_server (Zabbix) 3.0.1
Revision 58734 26 February 2016, compilation time: Feb 28 2016 07:18:05
-
Sprint 50 (Mar 2019), Sprint 51 (Apr 2019), Sprint 52 (May 2019), Sprint 53 (Jun 2019)
I've got a server which generates some metrics for a period 9AM – 12AM. Items is generated from LLD and lost resources kept for 30 days. Most of items live only for one day, so if trigger does not go off before midnight it stays in 'problem' state until it deleted in 30 days, this kind of triggers is acknowledged manually in the evening.
To prevent zabbix from alerting unacknowledged stuck triggers all night long there is a time period condition in action that sends emails – 1-5,09:00-23:55. If trigger was ack'ed zabbix starts to send emails after 23:55 and never stops until trigger is disabled/deleted.
How to reproduce:
1) Create LLD rule with some items and triggers
2) Create action with time period
3) Wait for LLD and items creation
4) Make trigger go on
5) Force item to become 'Not supported' (Received value [] is not suitable for value type [Numeric (float)])
6) Ack the trigger
7) Wait for action time period to end, zabbix will start to alert.