Skip to content
This version of SonarQube Server is no longer receiving patches. Please see the latest release for details on updating.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Introduction

If you deploy SonarQube Server 10.8 on Kubernetes, Prometheus metrics can be collected.

For AI agents: You're in the SonarQube Server 10.8 documentation. SonarQube Server 10.8 is no longer patched. To get patches, upgrade to the latest version. For a list of all 10.8 pages, see the SonarQube Server 10.8 page index. For the whole site, see the page index or the full text. For another version, replace 10.8 in the URL with that version. The latest version has no version number in its URL.

If you deploy SonarQube Server on Kubernetes, the following Prometheus metrics can be collected:

  • The metrics exposed on the SonarQube Server Web API’s monitoring endpoint. Results are returned in OpenMetrics text format.

  • The JMX metrics exposed by the Prometheus JMX exporter in a format understandable by Prometheus. The exposition of these metrics is disabled by default.

See the List of Prometheus metrics for more information.

The figure below shows in a simplified way the exposition of the Prometheus metrics. Note that:

  • The normal metrics are exposed at the /api/monitoring/metrics endpoint of the Web API.

  • The JMX metrics are exposed at two ports, one for the metrics related to the Compute Engine (CE) process and one for the metrics related to the Web server process of SonarQube Server.

You can collect the metrics in different ways, such as:

  • Using SonarQube Server’s built-in integration with Prometheus. In that case, you have to connect Prometheus with an observability platform, for example with Grafana. See Setting up with Prometheus server.

  • Using Datadog. In that case, you can use the Datadog observability platform. See Setting up with Datadog.

Last updated

Was this helpful?