Thank you for your reply. The problem appears daily and we check that there is no analysis at same time (big or little). Thanks for the information, if there is no Sonar process, we’ll check another host processes.
Thank you again
I would advise to approach this from a simple monitoring/troubleshooting angle, independently from SonarQube at the top being:
use your OS monitoring tools to verify whether it’s actually one of SonarQube’s Java process who is eating up the CPU
if you narrow it down to SonarQube, then focus more specifically on JVM monitoring, to understand how processes’ resource consumption whenever you observe abnormal behaviour