> 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/10.7/user-guide/code-metrics/monitoring-project-metrics.md).
# Monitoring project metrics
You can view the values of all [Metric definitions](/sonarqube-server/10.7/user-guide/code-metrics/metrics-definition.md) in your project and you can view the value history of one or several code metrics in your project.
## Viewing the values of all code metrics
1. In the top navigation bar, click **Projects** and then click the project you want to monitor.
2. In the project navigation bar, click **Measures**.
## Viewing the value history of one or several metrics
1\. In the top navigation bar, click **Projects** and then click the project you want to monitor.
2\. In the project navigation bar, select **Activity**. The left sidebar contains the list of code scans performed on your project.
3\. In **Filter events**, you can filter the scans list by event type (see **Event types** in [Viewing project activity](/sonarqube-server/10.7/user-guide/viewing-projects/activity-and-history.md)).
4\. Issues are shown in the graph by default. To change the metrics shown, click **Issues** and select another metric category in the drop-down list.
5\. 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. The selected metrics are displayed in one or several graphs 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 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/10.7/user-guide/code-metrics/monitoring-project-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.