oxidecomputer / oxidecomputer/cluster-api-provider-oxide
Logging Improvements
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2
- Forks
- 1
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 6
Description
We are only using Error and Info logging today. Many of our logs should not be firing at Log and instead should move to a Debug level. Kubebuilder scaffolds with logr so there are only Info() and Error() named logging levels and the rest are integer verbosity levels.
- Investigate if we should switch backend logger or use the integer verbosity levels.
- Recategorize logs as appropriate
- Reduce repetitive logging during fast reconciles.
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 tracing the Kubebuilder reconciliation entry points and the existing logr calls to identify Info-level messages that repeat during fast reconciles. Decide whether integer verbosity levels or a different backend logger fits the provider, recategorize the affected logs, and verify that repetitive reconciliation output is reduced without losing useful errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100