Set up logging properly
Rocket's logger was the only one, so messages from the daemons depended on it having launched, and most messages bypassed logging with println!. - Install env_logger at startup: level from log.level (LOG_LEVEL), with RUST_LOG overriding it. Rocket's per-request logs and sqlx's Postgres notices are kept to warnings. - Under systemd, prefix lines with their syslog priority so journald records levels (journalctl -p warning works). - Replace every println! with a log macro at a fitting level. - Recurring failures are a warning when they start or change, debug while they repeat, and an info message when they recover. - Listenbrainz errors are readable: an unknown user is "Listenbrainz user "x" doesn't exist" rather than a JSON decode error, and a period without stats yet (204) leaves the playlist alone instead of failing to decode. The UI's Refresh shows the same messages. - Warnings name the playlist or rule they're about. - Songs missing from the library are debug output, not errors every tick. - Daemons no longer run twice at startup (interval's first tick is immediate), and a failing playlist rule or daemon is logged instead of panicking the task. - Subsonic errors display as messages rather than Debug output. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018opPJMJjLWr4RqdG6vuK6p
This commit is contained in:
14 files changed
+436
-67
No files matched your search
@@ -40,6 +40,17 @@ podman run --rm \
|
||||
|
||||
The package is written to `target/debian/`.
|
||||
|
||||
### Logging
|
||||
|
||||
playlistd logs to stdout. Set the level with `log.level` in `playlistd.toml` (or `LOG_LEVEL`):
|
||||
`error`, `warn`, `info` (the default), `debug` or `trace`. `RUST_LOG` overrides it for finer control,
|
||||
e.g. `RUST_LOG=playlistd=debug` to also see which top songs couldn't be found in your library.
|
||||
|
||||
Under systemd, lines are tagged with their priority, so `journalctl -u playlistd -p warning` shows
|
||||
just the problems. A failure that keeps happening (say, a tracked playlist for a Listenbrainz user
|
||||
that doesn't exist) is logged as a warning once, and again only if the error changes; recovering
|
||||
from it is logged too.
|
||||
|
||||
## How to use
|
||||
|
||||
Each of these will work best when your music library is well organised with Musicbrainz metadata.
|
||||
|
||||
Reference in new issue
Block a user