[ZBX-15594] Trigger in problem state keep hold dependent triggers in history view Created: 2019 Feb 05  Updated: 2019 Feb 06  Resolved: 2019 Feb 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F), Server (S)
Affects Version/s: 4.0.4
Fix Version/s: None

Type: Problem report Priority: Minor
Reporter: Dmitriev Evgeniy Assignee: Zabbix Support Team
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1.png     PNG File 2.png     PNG File 3.png     PNG File 4.png     PNG File 5.png    

 Description   

Follow ZBXNEXT-4883, now the main trigger keep hold state of depend trigger in history view.

For example:

1) zabbix_sender -z 127.0.0.1 -p 10051 -s test -k value -o "1"

2) zabbix_sender -z 127.0.0.1 -p 10051 -s test -k value -o "1"

3) zabbix_sender -z 127.0.0.1 -p 10051 -s test -k value -o "0"

4) If manually close the main trigger, then depent trigger is keep active state

5) And active in problems view



 Comments   
Comment by richlv [ 2019 Feb 05 ]

Seems like the expectation was that manually closing a problem would also close all dependent problems, is that correct?

Comment by Dmitriev Evgeniy [ 2019 Feb 05 ]

Not quite right, manual closing shows a possible result of the fact that the dependent trigger did not close automatically after receive "0".

Comment by Glebs Ivanovskis [ 2019 Feb 05 ]

Same issue if dependent triggers don't use same items as master trigger. Dependent triggers are not calculated while master trigger is in problem state and don't get recalculated when master trigger resolves, unless their item gets a new value at the same time.

Expectation is that dependent triggers are simply hidden during master problem, but the actual behaviour is as if they were disabled.

Comment by Dmitriev Evgeniy [ 2019 Feb 05 ]

Thanks for the answer. So it just wasn't visible before, then depend triggers were hidden. Sorry for troubling.

Generated at Fri Mar 29 11:03:28 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.