‘/api/issues/search?componentKeys=’+project_name+‘&s=FILE_LINE&resolved=false&p=’+str(page)+‘&ps=400&facets=owaspTop10%2CsansTop25%2Cseverities%2CsonarsourceSecurity%2Ctypes%2Cassignees&additionalFields=_all&timeZone=Asia%2FCalcutta’ this is the api used.
This is triggered in a loop by incrementing the page for a project with more than 13000 issues. After 10000 issues I am getting 400 as s tatus code when made this api call. I would like to know the reason
Hey there.
As requested in the template post, what version/edition of SonarQube are you using?
Sorry for not specifying.
we are using sonarqube community edition 8.9
Thanks.
First of all, your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:
8.9 → 9.9.2 → 10.2.1 (last step optional)
You may find these resources helpful:
- Upgrade Guide
- LTS-to-LTS Upgrade Notes for 7.9 to 8.9
- LTS to LTS release upgrade notes for 8.9 to 9.9
Secondly, in either version, in order to retreive more than 10,000 results, you’ll need to get a bit creative about filtering (by issue type, severity, creation date…). All filters you can use in the Web API are available in the relevant Web API documentation.
I will upgrade the sonarqube to the latest version. Even after filtering I am getting issues more than 10,000(i.e., the mutations related bugs). So just wanted to know the limit which might help us restricting the code of lines for an individual project to be analysed.