Logfiles take up too much space by default

[lukehmcc]

Description

renterd is rather spammy with logs by default and this is problematic. Multiple times I have left renterd going in it's default configuration and two months later am out of disk space because the logs take up 60GB+. This is not an ideal default configuration. I understand you can change log level, but the defaults are too spammy. Either this should be changed or there should be a set level, lets say 1-10GB, where it will delete the old log data as to not overflow a disk.

Version

v1.1.1

What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?

debian 12

Anything else?

No response

[NickJH]

Use logrotate?

[lukehmcc]

Use logrotate?

I mean, yes, that would solve the problem. But my point is that the default configuration leads to problems. Whether the team wants to implement log rotation or changing what the default log level is doesn't matter as much as just making it so I don't get 60GB log files after a month or two.

[NickJH]

Then perhaps change the default to log to stdout and not to file. On Debian 12 this just logs to the journal. If you then want a log to a conventional file, you need to install something like rsyslog and add an rsyslog configlet, but on its own, journalctl will control the size of the journal.

[n8mgr]

I think the first order of business is reducing the verbosity of the default level. Just from a quick glance at calls to log.Info well over half of them should realistically be changed to Debug or removed entirely.