[ZBXNEXT-5251] Extend widget "Problems by severity" with aggregated view Created: 2019 May 31  Updated: 2024 Apr 10  Resolved: 2019 Aug 23

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: 4.4.0alpha2, 4.4 (plan)

Type: Change Request Priority: Trivial
Reporter: Aleksandrs Larionovs (Inactive) Assignee: Vasily Goncharenko (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: GIF File IE11_PBS_HA.gif     PNG File Screenshot from 2019-08-05 14-17-18.png    
Issue Links:
Causes
causes ZBX-16812 Problems by severity widget problem d... Closed
causes ZBX-16488 Problems by severity (totals) padding Closed
causes ZBX-16572 Incorrect text color in dark theme in... Closed
Sub-task
Team: Team D
Sprint: Sprint 55 (Aug 2019), Sprint 53 (Jun 2019), Sprint 54 (Jul 2019)
Story Points: 2

 Description   

Summary

Smooth migration from screens to dashboards requires some changes. Functionality of the existing screen element "Trigger info" should remain supported.

Zabbix acceptance

 
Existing widget "Problems by severity" will support aggregated view

  • New attribute: View (Show host groups, default, or Totals). A better naming can be selected at design phase.
  • If Totals is selected
    • The widget will display number of problems per severity in one row or one column same way as it is displayed now for screen element "Trigger info"
      • The only difference is that we will take data from Problems not from Triggers and no information about OK status will be available 
        • Zeros must be displayed as well. For example, if we have zero Average problems than 0 will still be displayed on a background with solid color corresponding to Average severity
      • New attribute will be enabled: Layout (horizontal, default, or vertical)
      • The following attributed will be disabled: Hide groups without problems
        Documentation must be updated

Nonfunctional requirements

  • Must create early UX/UI design prototype

Use cases

  • I don't want to lose existing functionality when migrating from screens to dashboards

Decisions made

  • No information about status of triggers will be available, it is all about problems. Therefore it is a functional regression.


 Comments   
Comment by Vasily Goncharenko (Inactive) [ 2019 Jun 18 ]

Implemented in development branch feature/ZBXNEXT-5251-4.3

Comment by Vasily Goncharenko (Inactive) [ 2019 Aug 06 ]

Implemented in:

  • 4.4.0alpha2 (master) d7f5b34d48c
Comment by Alexander Vladishev [ 2019 Aug 23 ]

Updated documentation

Generated at Wed Apr 24 20:23:48 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.