[ZBXNEXT-1765] Improved Screens navigation and management Created: 2013 May 30  Updated: 2021 May 21

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

Type: Change Request Priority: Major
Reporter: Cristian Assignee: Unassigned
Resolution: Unresolved Votes: 17
Labels: screens, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBXNEXT-2437 accessing host screens Closed
is duplicated by ZBX-6639 Improved Screens navigation and manag... Closed

 Description   

Hi,

I think the current way the screens are implemented is making hard to use them.

On management side:

  • The focus should be on creating screens within templates
  • The general screens (as they are) should have the option to include templated screens if the hostname has assigned a template with screens

On consulting/review these screens I think:

  • Monitoring->Screens should have a way to select Host as well, not to only display "general" screens
  • If a host has included a template with a screen then when navigating the Monitoring->Screens and picking the proper host it should be displayed the templated screen
  • As well should be a way to switch between hosts having same screen. So less clicks to navigate to graphs
  • As well, I think the zoom bar used on zabbix is harder to understand/use. Having select boxes as on Cacti is much better

Basically on navigation/review side of graphs I found Cacti much superior and somehow we should follow the same or improved navigation/review pattern.



 Comments   
Comment by alex dekker [ 2017 Dec 22 ]

Host screens are inexplicably difficult to find. There should be a link to them from the Screens screen.

Comment by Alexei Vladishev [ 2021 May 21 ]

I think it has been improved significantly in 5.4 by merging of screens (global and template-level) into dashboards. Less confusing and much more user friendly!

Generated at Thu Apr 25 17:02:47 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.