[ZBXNEXT-4825] Monitoring -> Problems: Export to CSV from all pages by default Created: 2018 Oct 24  Updated: 2024 Apr 10  Resolved: 2019 Dec 09

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 4.0.0
Fix Version/s: 4.0.15rc1, 4.4.2rc1, 5.0.0alpha1, 5.0 (plan)

Type: Change Request Priority: Trivial
Reporter: Aigars Kadikis Assignee: Mārtiņš Tālbergs (Inactive)
Resolution: Fixed Votes: 13
Labels: csv, export, pagination, problem
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File export-to-csv-from-all-pages.png    
Issue Links:
Duplicate
is duplicated by ZBX-14484 Export events only 50 rows Closed
Sub-task
part of ZBXNEXT-4807 Ability to select all filter results ... Open
Team: Team B
Sprint: Sprint 57 (Oct 2019), Sprint 58 (Nov 2019)
Story Points: 1

 Description   

Hi,

Please configure "Export to CSV" button to grab the data from all the pages inside: Monitoring -> Problems view.

Currently, on 4.0.0 it always extracts the data only from the first page (50 records).



 Comments   
Comment by Brian Sheth [ 2019 Aug 14 ]

What was included in 2019 Apr update? I don't see any new update here.

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Oct 18 ]

IMPLEMENTED in development branch feature/ZBXNEXT-4825-4.0

Comment by Alex Castillo [ 2019 Oct 18 ]

Hi All:

any work arround, can you share a SQL query so we can get the list directly from mysql, waiting for the fix.

thank you!

 

Alex.

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Oct 21 ]

Hi acastillov this branch currently has implementation that solves problem. This commit, if applied, exports CSV from all pages (Administration -> General -> Limit for search and filter results setting is still obeyed).
This task just received spec sign-off and we will have to wait on QA testing for this to be merged.

Comment by Mārtiņš Tālbergs (Inactive) [ 2019 Oct 30 ]

Available in:

Comment by Alexander Vladishev [ 2019 Dec 09 ]

Updated documentation:

Generated at Sun May 24 19:05:43 EEST 2026 using Jira 10.3.18#10030018-sha1:5642e4ad348b6c2a83ebdba689d04763a2393cab.