Webhooks sonarqube

When I tried using webhooks I am getting data like project name, quality gates details etc… is there any possible way to get issues details and added debt?

Here there.

There is not, although you could always make API calls after receiving the webhook (the Web API is documented in the footer of your instance).

What would you use the issue details for?

I am trying to collect the stats of each projects in my server, we have certain restrictions for our server in which sonarqube is deployed. So we are in a situation where we cannot make api calls but only use webhooks. Is there any other way to collect the issues count?

No – in order to extract more details from SonarQube, you would need to be able to make API calls.

And, I’m really curious to know what value you expect to get extracting the values rather than seeing them in the SonarQube server itself.

We have a large number of projects in our sonarqube server, it is difficult for me to view the issues for individual projects. So we are trying to fetch the count of the issues and project name as a graph, to identify issues in individual projects that helps us to prioritise projects as we have a large amount of issues to be solved for each projects.

Thanks for the explanation.

While it’s understandable that you’d like to visualize the overall number of issues in a way that can help you prioritize work, I think it’s important to focus on the Clean as You Code philosophy, rather than the total count of issues across projects.

Clean as You Code is based on the idea that the best time to fix issues is when they’re introduced—typically when the code is fresh in the developer’s mind. If everyone on the team adopts this practice, you can ensure that the new code committed to the codebase meets your quality standards and does not introduce any additional issues.

Trying to fix all issues in a large codebase all at once could be a daunting, time-consuming task that might not bring immediate value to your projects. However, maintaining the cleanliness of new code means you’re continuously improving the codebase. Over time, this will help reduce the overall issues in your projects without having to fix all existing problems in one go. It’s about steady, incremental improvement.

And, you might be interested in the Portfolios feature of SonarQube Enterprise Edition, which allows for some aggregate reporting (on both new and overall code)