[ZBX-18485] Max 20 graphs on Monitoring>Hosts>Graph Created: 2020 Oct 13  Updated: 2020 Dec 18  Resolved: 2020 Dec 18

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

Type: Problem report Priority: Trivial
Reporter: Marek Krolikowski Assignee: Zabbix Support Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive files.zip     PNG File rows-per-page.png    
Issue Links:
Duplicate
duplicates ZBX-17748 Monitoring->Hosts->Graphs shows only ... Closed

 Description   

Hello Guys,

After upgrade from version 3.0 to 5.0 i got strange problem with Graph.

When I enter monitoring>hosts>Graph I see that for example, 28 graphs are assigned to the host. When I click the graph, I see only 20 graphs. And there is no way to click "next page" or something like this i just don't see option to see rest of 8 graph.

Now i use Zabbix version 5.0.4.

 Comments   
Comment by Aigars Kadikis [ 2020 Oct 15 ]

Thank you for reaching out. Please attach a full-page screenshot of the problem:

1) A host contains 28 graphs

2) Only 20 graphs available at Monitoring => Hosts => Graphs section

+ have a look what is row limit configured for current user:

 

Comment by Marek Krolikowski [ 2020 Oct 15 ]

I give you screenshot at attachment - please take a look.

My friend give me workaround.

To change in defines.inc.php:

ZBX_MAX_GRAPGS_PER_PAGE from 20 to 30...

But will be awsome if there will be option to configure in User settings like Rows per page.

 

Best Regards

TaKeN

 

Comment by Aigars Kadikis [ 2020 Nov 12 ]

Hi Marek,

Some settings from defines.inc.php have been already migrated to GUI in 5.2 release, but not your requested one.

Please register a future request at ZBXNEXT project for this functionality.

I will close this issue as 'Won't fix' as the functionality on 5.0 is by design.

Comment by dimir [ 2020 Dec 18 ]

Duplicate of ZBX-17748

Generated at Tue May 20 08:23:45 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.