> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2025.3/server-installation/on-kubernetes-or-openshift/set-up-monitoring/introduction.md).

# Introduction

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

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](https://prometheus.io/docs/instrumenting/exposition_formats/#openmetrics-text-format) 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](/sonarqube-server/2025.3/server-installation/on-kubernetes-or-openshift/set-up-monitoring/prometheus-metrics.md) 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.

<figure><img src="broken://spaces/KXW79zfYFiA8incTvwZK/files/okFdacz4tG683abqba2k" alt="Collecting Prometheus metrics in SonarQube"><figcaption></figcaption></figure>

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](/sonarqube-server/2025.3/server-installation/on-kubernetes-or-openshift/set-up-monitoring/prometheus.md).
* Using Datadog.\
  In that case, you can use the Datadog observability platform.\
  See [Setting up with Datadog](/sonarqube-server/2025.3/server-installation/on-kubernetes-or-openshift/set-up-monitoring/datadog.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.3/server-installation/on-kubernetes-or-openshift/set-up-monitoring/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.