Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase debuggability with higher verbosity level ("debug") logs #1660

Open
azych opened this issue Jan 29, 2025 · 0 comments
Open

Increase debuggability with higher verbosity level ("debug") logs #1660

azych opened this issue Jan 29, 2025 · 0 comments

Comments

@azych
Copy link
Contributor

azych commented Jan 29, 2025

Currently both the operator-controller as well as catalogd have barely any (2 to be exact) log messages that aren't being logged at a default (0) log verbosity level.
It might be beneficial to increase debuggability of the project by inserting additional, higher log verbosity level ("debug") type messages that would contain additional context and would make for better understanding the detailed flow of what's happening, eg. in/out function arguments and return values, payload(s) dumping etc.

Technically with logr this can be done by declaring a non-default/higher log verbosity level via the .V() method, see https://pkg.go.dev/github.com/go-logr/logr#hdr-Verbosity for details.

@azych azych changed the title Increase debuggability with higher verbosity level ("Debug") logs Increase debuggability with higher verbosity level ("debug") logs Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant