oxidecomputer / oxidecomputer/dendrite
Consider demoting dropshot logging to debug
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
All dpd dropshot requests are currently logged at the info level. With the interaction model between tfportd and dpd this makes for a very noisy log that's difficult to work with. We should consider demoting these messages to the debug level so looker -l info is easier to work with.
Contributor guide
No contributing guide indexed for this repository
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 by locating the dpd Dropshot request logging and reading how requests from tfportd are represented. Use looker -l info to observe the current noise, then verify that these messages no longer appear at info while remaining available at debug.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100