> 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/user-guide/code-metrics/monitoring-metrics.md).

# Monitoring metrics

SonarQube Server 2026.5 offers various tools to monitor and compare code metrics for your project, application and portfolio.

You can view the values of all code metrics in your project, application or portfolio, as well as the value history of one or several code metrics in your project. Portfolios are available starting in [*Enterprise Edition*](https://www.sonarsource.com/plans-and-pricing/enterprise/).

## Viewing the values of all code metrics <a href="#all-metrics" id="all-metrics"></a>

<figure><img src="https://content.gitbook.com/content/mX1WoFEHhJp6VdSbyTDi/blobs/P9oTeHUKUQFKybZo5I2g/project-measures.png" alt="Retrieving the measures page"><figcaption></figcaption></figure>

1. Retrieve your project, application or portfolio.
2. Go to **Measures**.

## Viewing the value history of one or several metrics <a href="#value-history" id="value-history"></a>

<figure><img src="https://content.gitbook.com/content/mX1WoFEHhJp6VdSbyTDi/blobs/3qNZo1ziCT5Ed7gYTndz/project-activity%20(1).png" alt=""><figcaption></figcaption></figure>

1. Retrieve your project, application or portfolio.
2. Go to **Reporting** > **Activity**.
3. The left sidebar contains the list of code scans or snapshots.
4. In **Events filter**, you can filter the scan results by event type. See **Event types** in [Viewing project activity](/sonarqube-server/user-guide/viewing-projects/activity-and-history.md) for more information.
5. Use the **Date range filter** to narrow down the results to a specific date range.
6. Select the **Graph type**: **Issues** (default), **Coverage**, **Duplications**, **Custom**.
   1. Select **Custom** if you want to monitor other metrics.
   2. Click **Add metric** and select from the drop-down list the metrics you want to monitor. The selected metrics are displayed in one or several graphs so that you can compare them.
   3. Hover over the graph to display the tool tip with additional information.


---

# 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/user-guide/code-metrics/monitoring-metrics.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.