oxidecomputer / oxidecomputer/steno
Have you considered changing the log library to tracing?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
First of all, I would like to thank the developer for providing the excellent rust library of steno. During my use, I found that the entire log is based on slog. I learned about slog and it is also a very excellent library. However, most of the applications and libraries I built, or almost all of them, are using tracing, and the official slog library no longer recommends using slog but recommends tracing. I hope you can consider changing the log library to tracing.
In my current project, I am making an intermediate layer to convert the steno log library to the tracing library. Although it works, it is a lot more work.
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
The issue does not name any files, tests, or entry points. Start by locating steno's slog integration and reviewing how logging is exposed across the library; define the migration boundary and compatibility expectations before changing anything. Done would require the library to use tracing without breaking its existing logging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100