You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my full node, I am seeing my rolling log files fill up and overwrite in about 4-5 hours when the config.yaml file is set to log "INFO" level messages. I know that the Log File Management entry in the link below shows that only the last seven (7) log files are archived, resulting in 160MB maximum for old data.
Can you update code and allow an entry to the config.yaml file for keeping the last X number of log archives or setting new maximum of X MB of log files to keep? Or would it be dependent on the user to backup the log files are they are turned over?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
On my full node, I am seeing my rolling log files fill up and overwrite in about 4-5 hours when the config.yaml file is set to log "INFO" level messages. I know that the Log File Management entry in the link below shows that only the last seven (7) log files are archived, resulting in 160MB maximum for old data.
Log File Management
Can you update code and allow an entry to the config.yaml file for keeping the last X number of log archives or setting new maximum of X MB of log files to keep? Or would it be dependent on the user to backup the log files are they are turned over?
Beta Was this translation helpful? Give feedback.
All reactions