Sudden spike in callouts to SonarQube server

SonarQube
,
1

  • which versions are you using (SonarQube, Scanner)
    SonarQube server version: 9.9.1.69595
    Scanner version: 4.4.0.2170

  • how is SonarQube deployed: Docker in Kubernetes

  • what are you trying to achieve
    How can we debug where the sudden spike in request count originates? The request count jumped from 5,600 requests in 7 days, to 310k requests in 7 days almost overnight.

There was no significant increase in project count.

I’m trying to rule out increase in usage. I’ve visited the Github repos of the projects that logged the most api/ce/component?component={repo} HTTP/2.0 request, and their GHA actions are consistent with the previous weeks’.

  • what have you tried so far to achieve this
    Are there other leads we can explore to determine where the requests are coming from? Especially these ones which give no indication of which repo or pull request or push event that trigger them:
GET /api/rules/search.protobuf?f=repo,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile={profileId}&ps=500&p=1 HTTP/2.0

The only useful information I can see is useragent being ScannerCLI/4.4.0.2170

Thanks!

2

Hey there.

Don’t the access.log files have an IP address and timestamp associated with them? That should be a pretty safe place to start… especially if you’re trying to rule out GitHub Actions runners, for example.