Adopt `log/slog` for diagonostics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
logrus is dead, long live slog.
But in all seriousness, this library has stayed super trim and basically taken no dependencies that aren't in my control. Now that there's a reasonable option for logging in the standard library, adopting it and adding a bunch of things that would help when diagnosing problems in https://github.com/marstr/baronial makes sense.
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 inventorying the repository's current logrus usage and reading Go's log/slog documentation. Review the linked marstr/baronial project for the diagnostic needs described in the issue, then define the logging scope and acceptance criteria before changing anything; done means the agreed diagnostics are provided without the old logging dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100