-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
slogfiles grow without bound, contrary to devops norms a la logrotate #3779
Comments
@michaelfig I'm inclined to take the SwingSet label off this one, leaving it on the cosmic-swingset agenda. |
adding @dtribble in a customer role assignment |
In order to investigate what seems like unnecessary round-trips in the governance demo (#3869), I looked into the options here and found a couple that seem workable plus others that I would rather avoid: named pipe + multilog / svlogdThis option appeals to me:
add log rotation to swingset slogger with
|
Solved by @michaelfig (Flight Recorder #3742) |
Describe the bug
By setting
$SLOGFILE
or$SOLO_SLOGFILE
, operators can produce detailed diagnostics about swingset events. Unfortunately, these files grow without bound, which is awkward for the node operators and for data analysis.Expected behavior
logrotate is a norm for splitting logfiles into manageable pieces.
Ideally, these files would be split on block boundaries.
Additional context
originally noted in #3630
cc @rowgraus @warner @FUDCo
The text was updated successfully, but these errors were encountered: