[ZBXNEXT-6502] Latest data page, do not list data if no host or host group specified Created: 2021 Feb 10  Updated: 2024 May 02  Resolved: 2024 Apr 30

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 5.0.8, 5.2.4
Fix Version/s: None

Type: Change Request Priority: Minor
Reporter: Aigars Kadikis Assignee: Zabbix Development Team
Resolution: Duplicate Votes: 4
Labels: latestdata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-02-10-12-39-07-881.png    
Issue Links:
Causes
Duplicate
duplicates ZBXNEXT-7743 Open Monitoring - Latest data without... Closed
Sub-task
Team: Team A
Sprint: Sprint 83 (Dec 2021), Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022), Sprint 87 (Apr 2022), Sprint 88 (May 2022), Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Prev.Sprint, S24-W16/17

 Description   

On a big installation, it would be good to have a checkbox for users to not allow filter data without specifying host group.

Suggested behaviour would be:

If we go to "Monitoring" => "Latest data" and the filtering is empty:

then nothing happens. Must specify at least one host group or hostname.

This behaviour should be customizable somewhere under the "Administration" section.

 

Right now, as a workaround, a user can use the search field to enter "Latest data" page for a "host" or "host group".

Sadly, new users can still overload the web server and database by accidentally hitting the "Latest data" page. We want to prevent this by having this checkbox.



 Comments   
Comment by Dace Petra (Inactive) [ 2024 Apr 30 ]

This issue has been solved in ZBXNEXT-7743.

Generated at Tue Apr 08 18:04:06 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.