[ZBX-18138] Unfiltered Trigger Overview not displaying some triggers Created: 2020 Jul 23  Updated: 2020 Aug 20

Status: Need info
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 5.0.2
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Matthew Glennon Assignee: Zabbix Support Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Attachments: PDF File Zabbix-Report.pdf    

 Description   

Steps to reproduce:

  1. Create dashboard displaying Tirgger Overview.
  2. Have another type of widget available to compare.
  3. Have a trigger occur.
  4. Observe missing trigger(s).

Result:
See Screenshots in attached PDF.
Expected:
I should see all active triggers like I used to. Problem started in either 5.0.1 or 5.0.2 if my memory serves me.

 Comments   
Comment by Matthew Glennon [ 2020 Jul 23 ]

Ugh. Typo in the title. "Trigger Overview". We're not Winnie the Pooh here. 🤦‍♂️

Comment by Valdis Murzins [ 2020 Jul 24 ]

The problem widget configuration is not exactly default.
And one of it's options is to display suppressed problems. Trigger overview widget, on the other hand, is not displaying suppressed problems.
Other thing to take into account is problem dependency. Is the missing trigger dependent on some other?

Comment by Matthew Glennon [ 2020 Jul 24 ]

Thank you for your reply.

None of the problems are currently suppressed and the missing triggers here (Restart Required) have no dependencies.

Comment by Aleksandrs Petrovs-Gavrilovs [ 2020 Aug 04 ]

Hello,

I see in the trigger overview you have "Show -> Recent" problems select, what if you select any problems, does it show all of them including the missing ones?

Best Regards,
Aleksandrs

Comment by Renats Valiahmetovs (Inactive) [ 2020 Aug 20 ]

We have noticed that this issue has not been updated for a long time. May we assume that this case is resolved? If it is not and requires additional work, please comment on the ticket and we will respond accordingly. Alternatively, we're going to change the state of the issue to Resolved in 14 days if we don't hear back from you.

Generated at Sat Mar 15 08:34:06 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.