open-feature / open-feature/flagd
Review all log lines to use structured logging
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
We should do this generally, and review all our logging to make sure it uses consistent, structured logging where relevant.
logger has WithFields which will be the best here. Structured logging please...
Originally posted by @erka in https://github.com/open-feature/flagd/pull/1865#discussion_r2769246835
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
No files or tests are named. Start by reviewing the repository's logging calls and the logger's WithFields support. Done means relevant log lines consistently use structured fields, but the issue does not define which lines or fields qualify.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100