> 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/introduction.md).

# Introduction

Automated code review and analysis in SonarQube Server 2026.1 uses various code metrics to evaluate code quality.

Code metrics reflect quantifiable qualities of your project. They can be used in quality gate definitions (for example, to set a condition on the total number of raised issues in the code). See [Understanding quality gates](/sonarqube-server/2026.1/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md) for more information.

The mode of your SonarQube Server instance, either [MQR mode](/sonarqube-server/2026.1/instance-administration/analysis-functions/instance-mode/mqr-mode.md) or [Standard Experience](/sonarqube-server/2026.1/instance-administration/analysis-functions/instance-mode/standard-experience.md), will determine which code metrics you see in the UI.

You can use different tools in the SonarQube Server to monitor and compare your project or portfolio’s code metrics.

{% hint style="info" %}
If you’re using an external monitoring system, you can retrieve the metric values through the [Web API](/sonarqube-server/2026.1/extension-guide/web-api.md).
{% endhint %}

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

* [Understanding measures and metrics](/sonarqube-server/2026.1/user-guide/code-metrics/metrics-definition.md)
* [Monitoring project metrics](/sonarqube-server/2026.1/user-guide/code-metrics/monitoring-project-metrics.md)
* [Monitoring portfolio metrics](/sonarqube-server/2026.1/user-guide/code-metrics/monitoring-portfolio-metrics.md)
* [Code metrics](/sonarqube-server/2026.1/instance-administration/analysis-functions/metrics-parameters.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 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/introduction.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.