> 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/quality-standards-administration/managing-quality-gates/tracking-inline-comments.md).

# Tracking in-line suppression comments

How to track the use of in-line suppression comments in the code in SonarQube Server 2026.2.

> **Note:** For C, C++, and Objective-C, we recommend using `sonar-resolve` to resolve issues directly in the code rather than suppressing them with `//NOSONAR`. See [Editing issues](/sonarqube-server/2026.2/user-guide/issues/managing.md#resolving-in-code) for more information.

Issue suppression on a specific line is possible in most languages by using the `//NOSONAR` comment or a comparable in-line suppression mechanism suited to the language.

To track the use of in-line suppression comments:

* For C, C++, Objective-C, PHP, T-SQL:
  * Use the rule `NoSonar` to track the use of the `NOSONAR` comment.
* For COBOL, PL/SQL:
  * Use the rule `NoSonarCheck` to track the use of the `NOSONAR` comment.
* For JavaScript, TypeScript:
  * Use the rule S1291 to track the use of the `NOSONAR` comment.
* For Java:
  * Use the rule S1309 to track the use of the `@SuppressWarnings` annotation.
* For Python:
  * Use the rule S1291 to track the use of the `NOSONAR` comment.
  * Use the rule S1309 to track the use of the `noqa` comment.
  * Use the rule S7632 to detect malformed `NOSONAR` and `noqa` comments.

For more information about the in-line suppression of issues for a given language, refer to the corresponding section in [Languages](/sonarqube-server/2026.2/analyzing-source-code/languages.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.2/quality-standards-administration/managing-quality-gates/tracking-inline-comments.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.