Controlling logging severity about bees HOT 5 CLOSED

grep works... ;)

...but filtering that originates within the bees process would be better (it wouldn't have to run the expression that generates the log message).

from bees.

When I implemented log levels passing to systemd, I also thought of filtering. But at that point, it made not quite sense because some logs without the others were sometimes out of context. Has this been fixed since? I know, you (@Zygo) reworked a lot of the loggings after my contribution so I guess it should be fine now.

from bees.

BTW @KristupasSavickas Since beesd passes log levels to the systemd journal, you can use journald filtering on it:

journalctl -p err -u [email protected]

from bees.

Logs at level 7 (DEBUG) are mostly "bees started iterating over the filesystem" and "bees finished iterating over the filesystem". Logs at level 6 (INFO) are individual dedup and copy operations. Levels 3-5 (ERR..NOTICE) are more significant problems like IO errors, exception traces, etc. Nothing in bees uses log levels 0..2.

PERFORMANCE and WORKAROUND warnings seem to be at the wrong level. They should probably be NOTICE (level 5) to distinguish them from routine dedup messages (requiring less attention) and other incidents like IO errors (requiring more attention).

I think any insufficient-context log messages should now be considered bugs: either add context to the individual message, or change the message log level to match the other messages that give context.

There might be a use for a lower-level log message level (i.e. move everything up so DEBUG is available for very verbose logging); on the other hand, such information would only be useful for people debugging the code, and anyone who is doing that can just modify the source to include the required extra information and revert the change when done.

from bees.

BTW @KristupasSavickas Since beesd passes log levels to the systemd journal, you can use journald filtering on it:

journalctl -p err -u [email protected]

To reduce unnecessary system log entries:

sudo systemctl edit [email protected]

[Service]
LogLevelMax=notice

from bees.