setting the stage....
monitoring tools like javamelody, appdynamics, and others help with runtime performance/tuning and are not directly related to code quality.
however, part of code quality could be associated with errors in logs, so tools like chainsaw and, more likely, splunk start to blur the lines.
then you review kind-of-like-but-not-quite tools like InfraRed and Glassbox where they are trying to improve the quality of the code in different approaches.
Question: How does Sonar compare/contrast to InfraRed and Glassbox, and/or does it work with/integrate/replace logging review tools such as splunk as it relates to code quality of the end-result solution?
Bonus Question: what other tools compliment Sonar if you were to setup the 'ideal' ecosystem towards a quality java solution?
I don't think that we can compare SonarQube with the tools you mentioned. It's like comparing apples and oranges. They both have vitamins but you can't tell which one to eat because you need them both. They're not even competitive to each other.
I'd prefer to see let's say some kind of integration (if it's meaningful) between SonarQube and these tools ( for instance there's a Javamelody plugin for SonarQube, as far as I know ) rather than think which one is better to use.
Regarding your bonus question my answer is :" it depends ". You can write different applications (desktop, web applications, cloud applications etc. ) using Java so it depends. It depends also on the context and other special requirements. For instance security real-time availability in some cases is really critical and in other don't matter. So my advise is to select those tools that cover the critical needs of each application.