Skip to content

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

Open
@azych

Description

@azych

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions