Sonarqube and sonarlint issues result is different


I am using sonarqube 6.7.5 and sonarlint 3.6 in eclipse mars.
I got different result in both of them. My sonarqube always got more. I have bind my sonarlint to my sonarqube server. Is there any other configuration?

I read some topics which has same problem but I still have not get answer. Please help. Thank you


Can you provide an example of a rule that is raising issue on SonarQube and not on SonarLint?


Hello, Here is attachment of example project.

In first picture, as you can see, my result on sonarqube is 656 but on my sonarlint is 644

On second picture, is result of one file. There are 3 rules which is not included in my sonarlint

The missing rules are from the “common rules” repository. These rules are kind of “meta rules”. They are creating issues based on other measures computed by SonarQube/SonarCloud.
We don’t evaluate those rules in SonarLint. For example, computing the coverage is both time consuming, and usually requires a good integration with the build process. This is not practical in the IDE.
Computing cross-project duplication can only be executed on server side, since it requires to access all code of all projects.

Long story short: this is expected behavior :slight_smile:

1 Like

I still has some question. In this project, it shows that sonarlint has 133 result, but on sonarqube overall is 685 while the leak preiod is 140.Is sonarlint scan leak period?

And I found that some issues is not scanned in sonar but it is scanned in sonarlint
Here on of the example: (I also have updated my binding)

No. SonarLint will report all issues, whatever is their date. Another common reason of difference is that the list of analyzed files can be different.

Regarding issues found in SonarLint but not in SonarQube, can you check that the file is correctly analyzed in both tools, and that is is not classified differently (as a test file only in one tool for example).
Test files have different rules applied.

Thank you, it helps much. :smile:

Hi Fanny,
Did you find the root cause for this issue?
I am also facing the same. Let me know if you find any resolution.


I am so sorry, but I still have not found the cause of this issue. Some of them are as explained on this topic by @Julien_HENRY , while the other is still unknown to me.

My team is quite busy, so nobody has the chance to look further yet.

Sorry :frowning_face: