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
Navigate to the Request Logs page in the application
Ensure there are more than 1000 log entries in the system (generate additional requests if needed)
Click the "Export" button to export the logs
Open the downloaded export file (CSV/Excel)
Count the number of rows in the exported file
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:
The system should inform users about the row limit before export
Allow users to filter/select date ranges on time ranges to stay within the limit
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-20 08:22:20 -05:00
@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...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
To Reproduce
Expected Behavior
The export should include all available Request Log entries, not just the first 1000. Alternatively, if there's a technical limitation:
@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...
@Fredkiss3 commented on GitHub (Dec 8, 2025):
@oschwartz10612 On it
@oschwartz10612 commented on GitHub (Dec 13, 2025):
Fixed in 1.13.0