Hello, our developers have been complaining about the SonarQube logs in the Jenkins console. They would like us to decrease the number of logs or have them removed altogether. They feel the logs make it more difficult when they are debugging code issues. We have the sonar.log.level set to info. Is there a way to reduce or totally alleviate the SonarQube logs?
Hi,
I’ll be honest: this is a new one on me. I would be helpful if you could pinpoint which parts of the logging your developers find overly verbose so we could get that addressed for everyone. And in the meantime setting sonar.log.level=WARN might work, although WARN isn’t actually listed as a recognized value for that parameter. Hopefully that’s because people usually want more information, not less, and not because it won’t work. 
HTH,
Ann
Hello,
There concern is the excessive amount of DEBUG logs. They also changed the sonar.log.level to WARN but it did not have much effect. How can we reduce the number of DEBUG logs in the Jenkins console?
Hi,
Debug logging is not the default. If you’re getting that then you’ve turned it on. So look for sonar.log.level and sonar.verbose in your analysis command line arguments and analysis properties, and remove them.
HTH,
Ann