oxidecomputer / oxidecomputer/opte
Audit logging from driver
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 77
- Forks
- 11
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 8
Description
warn!/note! messages will be outputted to the system log so let's make sure we're not polluting the log and only keeping necessary messages.
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 by locating the driver's uses of warn! and note! and reviewing how those messages reach the system log. Identify which messages are necessary and define the expected logging behavior; the work is done when unnecessary driver messages no longer pollute the system log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100