Daily CPU spike at 3 AM

[NicoB (Nicolas Bontoux)]

Hi there,

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

@NicoB

Monitor

Whatever the context, the minute one starts to look into performance, than monitoring comes in pair. There’s a good initial guide in the documentation . And ultimately those are pure monitoring/operational considerations for a Java application, i.e. first understand whether your performance feeling relates to system performance (CPU/RAM/IO), or application performance (product itself, but also interaction with other components like database),