> 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/user-guide/code-metrics/monitoring-metrics.md).
# Monitoring metrics
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
1. Retrieve your project, application or portfolio.
2. Go to **Measures**.
## Viewing the value history of one or several metrics
1. Retrieve your project, application or portfolio.
2. Go to **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/2026.2/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 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/user-guide/code-metrics/monitoring-metrics.md?ask=&goal=
```
`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.