[ZBXNEXT-3668] Option to group triggers with identical names in Monitoring -> Overview Created: 2017 Jan 26  Updated: 2017 Jan 26

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 2.2.16, 3.0.7, 3.2.3
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Ingus Vilnis Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: overview
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File 25012017_153305.jpg    

 Description   

Related to ZBX-9820 and ZBX-5072.

In older versions of Zabbix the triggers with different expressions but identical names in Overview page were grouped by those names. Agreed that this can cause confusion when used without knowing this behavior, however there were several use cases where this hidden feature was used intentionally.

As mentioned in ZBX-5072 this can be used in screens where same trigger has different severities thus achieving an effect where multiple triggers are displayed in one row just with different colors. User had intentionally configured the triggers that they don't overlap to not cause unexpected behavior on a single host.

This is how it looks now.

The page in particular use case was adapted to a wall mounted TV screen which has now become unusable because all triggers no longer fit in one screen. No, there is no option to use scrolling.

Please implement a control which can enable / disable the advantage of this grouping feature. Additionally it should be remembered in the user settings since screens are displayed automatically from selected URLs without the need to adjust the filtering by a user every time the page is opened.



 Comments   
Comment by richlv [ 2017 Jan 26 ]

seems to be a duplicate of ZBX-11743

Comment by Ingus Vilnis [ 2017 Jan 26 ]

Sigh. This is what happens when you start one issue in the morning and finish creating it by the evening. Coincidence because this functionality is not something what was changed yesterday.

Generated at Sat Apr 12 20:30:00 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.