Investigate in klogs
Open
Nobody has claimed this yet.
Toxiproxy
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
Make sure there are structured logs with possible deep log level.
Check logger from kubectl
Found https://github.com/kubernetes/community/blob/master/contributors/devel/sig-instrumentation/logging.md
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 reviewing the linked Kubernetes logging guidance and comparing the requested behavior with kubectl's logger. Identify the project's logging entry points and define what structured output and deeper log levels should cover; the work is done when those requirements are implemented and verified consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100