> 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.1/user-guide/code-metrics/monitoring-portfolio-metrics.md).
# Monitoring portfolio metrics
SonarQube Server 2026.1 offers various tools to monitor and compare code metrics for your portfolio.
Portfolios are available starting in [*Enterprise Edition*](https://www.sonarsource.com/plans-and-pricing/enterprise/).
To view the values of all code metrics in your portfolio:
1. In the top navigation bar, click **Portfolios** and then click the portfolio you want to monitor.
2. In the portfolio navigation bar, click **Measures**.
To view the value history of one or several code metrics in your portfolio:
1\. In the top navigation bar, click **Portfolios** and then click the portfolio you want to monitor.
2\. In the portfolio navigation bar, click **Activity**. The number of issues is shown in a graph.
3\. To change the metrics shown, click **Issues** and select another metric category in the drop-down list.
4\. Select **Custom** if you want to monitor other metrics: the **Add metric** drop-down list is displayed. Then, click **Add metric** and select in the drop-down list the metric(s) you want to monitor. A graph is displayed for each selected metric so that you can compare them.
---
# 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/2026.1/user-guide/code-metrics/monitoring-portfolio-metrics.md?ask=&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.
