[ZBX-12800] Problem with depended trigger after recovery Created: 2017 Sep 29  Updated: 2024 Apr 10  Resolved: 2017 Dec 01

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 3.2.8, 3.4.2
Fix Version/s: 3.2.11rc1, 3.4.5rc1, 4.0.0alpha1, 4.0 (plan)

Type: Problem report Priority: Blocker
Reporter: Aleksejs Petrovs Assignee: Andris Zeila
Resolution: Fixed Votes: 1
Labels: triggerdependencies, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS7, MariaDB 5.5.56


Attachments: PNG File 1.png     PNG File 2.png     PNG File 3.png     PNG File 4.png    
Issue Links:
Causes
causes ZBX-14313 Triggers with "All problems if tag va... Closed
causes ZBX-13586 With trigger correlation recovery eve... Closed
Duplicate
is duplicated by ZBX-13041 Actions ignored in escalation with tr... Reopened
Sub-task
Team: Team A
Sprint: Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 22
Story Points: 5

 Description   

If you will create 2 Triggers for the same item with different threshold then after the recovery only Main trigger will be in Ok status, but the Secondary will be in Problem state until the next new value will be received.

Example:
Host: test123
Item key: test
Type: Zabbix trapper
Trigger Main: ‍{test123:test.last()}<15
Trigger Secondary: ‍{test123:test.last()}<30

Please see screenshots in numerical order.

Regards,
Aleksejs!

 Comments   
Comment by Andris Zeila [ 2017 Oct 06 ]

Event processing was slightly reworked. Before trigger dependecy was checked before adding event to local queue, and trigger properties (state, value, lastchange) were updated after all events were processed. Now trigger dependency is ignored when adding event to local queue. Trigger dependency checks and property recalculation is done during event processing. Additionally propertes of triggers affected by global correlation are recalculated after event processing is done.

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-12800

Comment by Glebs Ivanovskis (Inactive) [ 2017 Oct 17 ]

A little comment on what is being fixed here. Before the fix server was creating two escalations for both master and dependent triggers instead of just one for master trigger. There are no plans to change Zabbix behaviour regarding dependent trigger update in case of master trigger recovery — this may or may not happen depending on trigger configuration and the exact way master trigger is recovering. We will try to document this in a bit more detail.

Comment by Glebs Ivanovskis (Inactive) [ 2017 Oct 25 ]

Successfully tested!

Comment by Andris Zeila [ 2017 Dec 01 ]

Released in:

  • pre-3.2.11rc1 r75255
  • pre-3.4.5rc1 r75256
  • pre-4.0.0alpha1 r75257
Generated at Fri Apr 26 13:03:02 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.