Description of problem: The default loglevel for the OLM operator is INFO instead of WARN. Logrus (the underneath logging package used) has a default of Info [0] when creating a new instance, and that may give too much output in this case. Moreover, the OLM have the `-debug` flag that sets the log level to `Debug` for troubleshooting, so having a default of Info seems too much for a default value. Version-Release number of selected component (if applicable): 4.6.15 How reproducible: View logs for OLM Steps to Reproduce: -- Actual results: Verbose output (due to info logs every few seconds) Expected results: Less verbose logs Additional info: Logrus (the underneath logging package used) have a default of Info [0] when creating a new instance, and that may give too much output in this case. Moreover, the OLM have the `-debug` flag that sets the log level to `Debug` for troubleshooting, so having a default of Info seems too much for a default value. [0]: https://github.com/sirupsen/logrus/blob/master/logger.go#L89 [1]: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/cmd/olm/main.go#L107-L111
Hi Felipe, We get a lot of valuable information by keeping the default log level of info and do not plan on changing that. There was already an effort as part of https://bugzilla.redhat.com/show_bug.cgi?id=1903034 to trim the logs coming from the underlying controller implementations in OLM which significantly reduced the volume of logs being produced. We could audit the code base and try to narrow down what is logged, but I do not believe that will have any real impact on the volume of logs produced any further. *** This bug has been marked as a duplicate of bug 1903034 ***