[ZBX-4100] Unexpected beahvior of Monitoring => Graphs Created: 2011 Sep 02  Updated: 2017 May 30  Resolved: 2012 Apr 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.5
Fix Version/s: None

Type: Incident report Priority: Major
Reporter: Marc Schoechlin Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-75 Add a "show all" option for viewing a... Open

 Description   

We are using Zabbix 1.8.5. We defined a monitoring template which is assigned to all 10 hosts of a host group "Customer Foobar".
The template contains a graph "CPU usage"

How to reproduce the problem:

  • Navigate to "Monitoring => Graphs"
  • Select the hostgroup "Foobar"
  • Select "all"
  • The graph-dropdown menu now contains 10 graphs with the identical name "CPU usage"

In my opinion the dropdown should only contain one entry "CPU Usage" and if i select this dropdown 10 graphs
(one for each host in the host group) should be displayed which one single time-slider for all hosts.
This is at least a usability bug

Regards Marc

 Comments   
Comment by Marc Schoechlin [ 2012 Jan 01 ]

I do not agree that this bug describes the same issue like ZBXNEXT-75 - its the opposite functionality

While ZBXNEXT-75 suggest that all available graphs of host should be viewed by a "Show all" selector - this bug suggests that a specific graph should be viewed for all
hosts of a group.

This is also a usability bug - viewing multiple identical graph names if the hosts-dropdown is set to "all" is confusing for users.

Comment by AG [ 2012 Feb 14 ]

I created the feature request ZBXNEXT-1120 to track the "wish" part contained in this bug report.

Comment by Alexey Fukalov [ 2012 Apr 19 ]

Close as ZBXNEXT-1120 was created for this feature.

Comment by Marc [ 2014 Apr 10 ]

Another way might be to prepend the corresponding (visible) host name to each graph list item

Generated at Thu May 02 00:30:30 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.