oxidecomputer / oxidecomputer/omicron
Allow more verbose logging in release binaries
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
This came up during the demo dry-run today. We had an issue whose resolution might have been helped by inspecting trace-level log messages, which we can get via slog-dtrace. However, most (all?) of our crates actually filter out anything above debug at compile time, using this slog feature. We should probably allow more verbose logging in release mode, at least until we have specific reason to remove them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the slog feature configuration linked in nexus/Cargo.toml and inspect how release builds configure logging across the crates. Use slog-dtrace to verify whether trace-level messages remain available in release binaries. Done means release binaries permit the requested verbose logging without removing existing logging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100