> 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/2026.2/server-update-and-maintenance/data-center-edition/monitoring.md).

# Monitoring

CPU and RAM usage on each node have to be monitored separately with an APM.

In addition, we provide a Web API `api/system/health` you can use to validate that all of the nodes in your cluster are operational.

* GREEN: SonarQube Server is fully operational
* YELLOW: SonarQube Server is usable, but it needs attention in order to be fully operational
* RED: SonarQube Server is not operational

To call it from a monitoring system without having to give admin credentials, it is possible to setup a system passcode. You can configure this through the `sonar.web.systemPasscode` property in `<sonarqubeHome>/conf/sonar.properties` if you’re using a traditional environment or through the corresponding environment variable if you’re using a Docker environment.

## Checking the cluster status in the UI <a href="#cluster-status" id="cluster-status"></a>

On the System Info page at **Administration > System**, you can check whether your cluster is running safely (green) or has some nodes with problems (orange or red).

<figure><img src="/files/GtyuUAkHk0DOPp0nUbp8" alt="Checking the system status of your SonarQube Server"><figcaption></figcaption></figure>

## Monitoring pending tasks <a href="#pending-tasks" id="pending-tasks"></a>

On the global Background Tasks page at **Administration > Projects > Background Tasks**, you can see the number of **pending** tasks as well as the maximum **pending time** for the tasks in the queue. This shows the pending time of the oldest background task waiting to be processed. You can use this to evaluate if it might be worth configuring additional Compute Engine workers (Enterprise Edition) or additional nodes (Data Center Edition) to improve SonarQube Server performance.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Setting up monitoring](/sonarqube-server/2026.2/server-installation/on-kubernetes-or-openshift/set-up-monitoring.md)
* [DCE topology](/sonarqube-server/2026.2/server-installation/data-center-edition/dce-topology.md)
* [Starting and stopping cluster](/sonarqube-server/2026.2/server-installation/data-center-edition/starting-stopping-cluster.md)
* [Improving performance](/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/improving-performance.md)
* [Scaling](/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/scaling.md)
* [Updating](/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/updating.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-server/2026.2/server-update-and-maintenance/data-center-edition/monitoring.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.