dosubot[bot] commented on issue #8174: URL: https://github.com/apache/incubator-devlake/issues/8174#issuecomment-2449516986
<!-- Greeting --> Hey @blackholll! I'm here to help you with any bugs, questions, or contributions. Let's get to the bottom of this together! <!-- Answer --> I found a similar closed issue that might be relevant to your situation: [Bug][SonarQube] failed to collect over 10000 data for issue](https://github.com/apache/incubator-devlake/issues/4592). This issue was resolved by a pull request that addressed the problem by dividing the issues into smaller groups to avoid exceeding the SonarQube API's result limit of 10,000 issues <sup>[[1]](https://github.com/apache/incubator-devlake/issues/4592)</sup>. The SonarQube plugin has certain limitations and configurations that might affect data collection for a large number of projects. Specifically, the plugin must divide issues into smaller groups based on "severity", "status", "type", "createdBefore", "createdAfter", and the file to which the issue belongs to manage within the API limits <sup>[[2]](https://github.com/apache/incubator-devlake-website/blob/main/versioned_docs/version-v0.21/Plugins/sonarqube.md)</sup>. Additionally, the default setting for connection calling frequency is 10,000 requests per hour, which can be adjusted to change the collection speed <sup>[[3]](https://github.com/apache/incubator-devlake/blob/main/config-ui/src/plugins/register/sonarqube/config.tsx)</sup>. However, reducing the frequency might not necessarily increase the amount of data collected if the issue is related to API limits or data classification. If you haven't already, you might want to ensure that the issues are being classified and collected according to these parameters to see if it resolves the problem. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
