[ZBX-17876] Graphs page displays "No data found" instead of the actual graph Created: 2020 Jun 05  Updated: 2020 Jun 05  Resolved: 2020 Jun 05

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

Type: Problem report Priority: Trivial
Reporter: rust equal Assignee: Renats Valiahmetovs (Inactive)
Resolution: Duplicate Votes: 0
Labels: graph, graphs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu Server 18.04.4, nginx 1.14.0-0ubuntu1.7, zabbix-frontend-php 5.0.1-1+bionic, zabbix-nginx-conf 5.0.1-1+bionic

Attachments: JPEG File 01.jpg    
Issue Links:
Duplicate
duplicates ZBX-17853 "No data found" clicking on graph in ... Closed

 Description   

Steps to reproduce:

  1. For example you need to configure 2 hosts with template "Template OS Linux by Zabbix agent". This hosts will have the "Network Interfaces" host screens.
  2. Open the page "Monitoring - Hosts".
  3. Click on "Screens" link of the first host. The host screen "Network Interfaces" of the first host will be opened.
  4. Now click on graph "Network traffic". The graphs page "Network traffic" of the first host will be opened.
  5. Go to the page "Monitoring - Hosts" again.
  6. Click on "Screens" link of the second host. The host screen "Network Interfaces" of the second host will be opened.
  7. Now click on the graph "Network traffic". You will see the graphs page with "No data found" message (see the screenshot)!
  8. To workaround this bug you need to go to "Monitoring - Hosts" page again and click the "Graphs" link of the second host. After that the graph page "Network Interfaces" of the second host will be opened correctly.

Result:
See screenshot...

 Comments   
Comment by rust equal [ 2020 Jun 05 ]

I think that the frontend remembers the hostid of the first host and when selecting the graph page of the second host, it looks for data in the hostid of the first host.

Comment by Renats Valiahmetovs (Inactive) [ 2020 Jun 05 ]

Hello!

Thanks for submitting this issue, it was however reported already and the development team is already working on it, so I will be closing this case as a duplicate

Generated at Mon Apr 07 02:29:47 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.