Skip to content

Reduce logging level from debug to trace#8

Open
vvv wants to merge 2 commits intoIdein:masterfrom
vvv:reduce-log-level
Open

Reduce logging level from debug to trace#8
vvv wants to merge 2 commits intoIdein:masterfrom
vvv:reduce-log-level

Conversation

@vvv
Copy link
Copy Markdown

@vvv vvv commented Jul 4, 2025

Rationale: consider an app that periodically checks if the CPU is throttled. The developer of that app may want run it with RUST_LOG=debug. They would be surprised and annoyed if their logs were flooded with messages irrelevant to their particular debugging need.

Check out this convention of logging levels.

Example of noise:

001_382ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_491ms DEBUG rpi_mailbox::kernel: 4,4,16
001_493ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_495ms DEBUG rpi_mailbox::kernel: 28:16
001_495ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_497ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_497ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_498ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_498ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_608ms DEBUG rpi_mailbox::kernel: 4,4,16
001_611ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_611ms DEBUG rpi_mailbox::kernel: 28:16
001_611ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_614ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_615ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_615ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_615ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_726ms DEBUG rpi_mailbox::kernel: 4,4,16
001_728ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_728ms DEBUG rpi_mailbox::kernel: 28:16
001_728ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_729ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_730ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_730ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_730ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_840ms DEBUG rpi_mailbox::kernel: 4,4,16
001_841ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_841ms DEBUG rpi_mailbox::kernel: 28:16
001_842ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_844ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_844ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_844ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_844ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_955ms DEBUG rpi_mailbox::kernel: 4,4,16
001_956ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_956ms DEBUG rpi_mailbox::kernel: 28:16
001_957ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_958ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_958ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_959ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_959ms DEBUG rpi_mailbox::kernel: buf_size: 4
002_068ms DEBUG rpi_mailbox::kernel: 4,4,16
002_070ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
002_070ms DEBUG rpi_mailbox::kernel: 28:16
002_070ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
002_073ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
002_073ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
002_073ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
002_073ms DEBUG rpi_mailbox::kernel: buf_size: 4
002_182ms DEBUG rpi_mailbox::kernel: 4,4,16
002_184ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0

vvv added 2 commits July 4, 2025 21:03
Rationale: consider an app that periodically checks if the CPU is throttled.
The developer of that app may want run it with `RUST_LOG=debug`.  They would
be surprised and annoyed if their logs were flooded with messages they don't
care about.

Check out this [convention](https://stackoverflow.com/a/2031209/136238)
of logging levels.

Example of noise:

```
001_382ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_491ms DEBUG rpi_mailbox::kernel: 4,4,16
001_493ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_495ms DEBUG rpi_mailbox::kernel: 28:16
001_495ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_497ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_497ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_498ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_498ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_608ms DEBUG rpi_mailbox::kernel: 4,4,16
001_611ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_611ms DEBUG rpi_mailbox::kernel: 28:16
001_611ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_614ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_615ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_615ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_615ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_726ms DEBUG rpi_mailbox::kernel: 4,4,16
001_728ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_728ms DEBUG rpi_mailbox::kernel: 28:16
001_728ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_729ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_730ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_730ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_730ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_840ms DEBUG rpi_mailbox::kernel: 4,4,16
001_841ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_841ms DEBUG rpi_mailbox::kernel: 28:16
001_842ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_844ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_844ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_844ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_844ms DEBUG rpi_mailbox::kernel: buf_size: 4
001_955ms DEBUG rpi_mailbox::kernel: 4,4,16
001_956ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_956ms DEBUG rpi_mailbox::kernel: 28:16
001_957ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
001_958ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
001_958ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
001_959ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
001_959ms DEBUG rpi_mailbox::kernel: buf_size: 4
002_068ms DEBUG rpi_mailbox::kernel: 4,4,16
002_070ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
002_070ms DEBUG rpi_mailbox::kernel: 28:16
002_070ms DEBUG rpi_mailbox::kernel: buf: [28, 0, 196678, 4, 4, 0, 0]
002_073ms DEBUG rpi_mailbox::kernel: buf: [28, 2147483648, 196678, 4, 2147483652, 983040, 0]
002_073ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
002_073ms DEBUG rpi_mailbox::kernel: req_resp_size: 4,4
002_073ms DEBUG rpi_mailbox::kernel: buf_size: 4
002_182ms DEBUG rpi_mailbox::kernel: 4,4,16
002_184ms DEBUG rpi_mailbox::kernel: data[..] 70 0 3 0
```
Comment thread Cargo.toml
edition = "2021"
name = "rpi-mailbox"
version = "0.4.0"
version = "0.4.1"
Copy link
Copy Markdown
Author

@vvv vvv Jul 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't forget to tag v0.4.1 and push the new tag to origin after merging this PR.

It might be a good idea to tag v0.4.0 as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant