← All insightsObservability

Monitoring and observability for SonarQube

Nir Geier, CodeWizard · 16 October 2025 · 3 min read · Intermediate

You cannot operate what you cannot see. Here is how to get useful signals out of SonarQube and turn them into alerts that mean something.

SonarQube statically analyzes code for bugs, vulnerabilities, security hotspots and 'code smells', and enforces a Quality Gate in CI so problematic changes fail the build.

What to watch

  • Enforce a 'new code' Quality Gate on every PR
  • Wire coverage reports into the scan
  • Triage security hotspots, don't blanket-ignore them
  • Track error rate and latency, not just up/down
  • Alert on symptoms tied to user impact

Operate and inspect

bash
sonar-scanner -Dsonar.host.url=http://localhost:9000 -Dsonar.token=$SONAR_TOKEN

Keep it healthy

  • Treat vulnerabilities and hotspots as gating, not advisory
  • Keep tokens scoped and rotate them

Want senior help putting SonarQube to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult