github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-15 21:31:24 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #2010] Request Logs export limited to 1000 rows maximum #2054

New Issue
Closed
opened 2026-04-16 09:00:39 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-16 09:00:39 -05:00
Owner
Copy Link

Originally created by @DaanHend on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2010

Describe the Bug

The Request Logs export functionality is limited to exporting a maximum of 1000 rows. When attempting to export logs that exceed this limit, only the first 1000 entries are included in the exported file, with no warning or indication.

Environment

  • OS Type & Version: Ubuntu latest
  • Pangolin Version: latest
  • Gerbil Version: latest
  • Traefik Version: latest
  • Newt Version: latest

To Reproduce

  1. Navigate to the Request Logs page in the application
  2. Ensure there are more than 1000 log entries in the system (generate additional requests if needed)
  3. Click the "Export" button to export the logs
  4. Open the downloaded export file (CSV/Excel)
  5. Count the number of rows in the exported file
  6. Observe that exactly 1000 rows are present, even though more logs exist in the system

Expected Behavior

The export should include all available Request Log entries, not just the first 1000. Alternatively, if there's a technical limitation:

  1. The system should inform users about the row limit before export
  2. Allow users to filter/select date ranges on time ranges to stay within the limit
  3. Display a warning when the export is truncated
Originally created by @DaanHend on GitHub (Dec 8, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2010 ### Describe the Bug The Request Logs export functionality is limited to exporting a maximum of 1000 rows. When attempting to export logs that exceed this limit, only the first 1000 entries are included in the exported file, with no warning or indication. ### Environment - OS Type & Version: Ubuntu latest - Pangolin Version: latest - Gerbil Version: latest - Traefik Version: latest - Newt Version: latest ### To Reproduce 1. Navigate to the Request Logs page in the application 2. Ensure there are more than 1000 log entries in the system (generate additional requests if needed) 3. Click the "Export" button to export the logs 4. Open the downloaded export file (CSV/Excel) 5. Count the number of rows in the exported file 6. Observe that exactly 1000 rows are present, even though more logs exist in the system ### Expected Behavior The export should include all available Request Log entries, not just the first 1000. Alternatively, if there's a technical limitation: 1. The system should inform users about the row limit before export 3. Allow users to filter/select date ranges on time ranges to stay within the limit 4. Display a warning when the export is truncated
GiteaMirror added the bug label 2026-04-16 09:00:39 -05:00
GiteaMirror commented 2026-04-16 09:00:41 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 8, 2025):

@Fredkiss3 Would you mind taking a look at this? Not sure how we want to handle larger file sizes...

<!-- gh-comment-id:3627329323 --> @oschwartz10612 commented on GitHub (Dec 8, 2025): @Fredkiss3 Would you mind taking a look at this? Not sure how we want to handle larger file sizes...
GiteaMirror commented 2026-04-16 09:00:41 -05:00
Author
Owner
Copy Link

@Fredkiss3 commented on GitHub (Dec 8, 2025):

@oschwartz10612 On it

<!-- gh-comment-id:3628511548 --> @Fredkiss3 commented on GitHub (Dec 8, 2025): @oschwartz10612 On it
GiteaMirror commented 2026-04-16 09:00:42 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Dec 13, 2025):

Fixed in 1.13.0

<!-- gh-comment-id:3649636103 --> @oschwartz10612 commented on GitHub (Dec 13, 2025): Fixed in 1.13.0
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#2054
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?