You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
azych
changed the title
Increase debuggability with higher verbosity level ("Debug") logs
Increase debuggability with higher verbosity level ("debug") logs
Jan 29, 2025
Currently both the
operator-controller
as well ascatalogd
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.The text was updated successfully, but these errors were encountered: