Logs csv export #80
Open
Logs csv export #80
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juliangiebel
requested review from
a team and
PJB3005
and removed request for
a team
Simyon264
reviewed
Jun 23, 2025
Simyon264
approved these changes
Jun 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements exporting admin logs as either a csv file or a gzip compressed csv file.
Files are exported using a hosted service and stored inside a configurable directory.
Old exports will need to be deleted using something like a systemd timer or a cronjob.
I tested this with 5 million logs, which results in a 500mb csv file and took a minute to export.
The export is limited to a single round or a configurable amount of days.
Even a day is likely to be over a gigabyte uncompressed so that'll have to be tested and adjusted after merging the PR