> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/quality-control/rules/metric-rules.md).

# Metric Rules

Metric Rules serve as the guidelines utilized for collecting metrics of a specific application type

1. Navigate to **`Rules`** -> **`Metric Rules`** <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FPwMIoRl93dQQz6ivs7tl%2Fmetric-rules.png?alt=media&amp;token=3663a5f1-6a2d-4305-b842-c420b6584682" alt=""><figcaption></figcaption></figure>
2. Details include -
   1. **`Name`** - Name of the rule
   2. **`Language`** - Language for which the rule is applicable. E.g.: Mule, API
   3. **`Return Type`** - Return type of the metric. Return types will be used for aggregating metrics
   4. **`Component`** - Indicates whether the metric is a **`FILE`** level or **`PROJECT`** level metrics
3. Click on **`Activate In Profile`** action to activate the metric in any of the Metric Profiles\
   &#x20;

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FkyYJuEHHjYJas0tRzGRR%2Factivate-metric-in-profile.png?alt=media&amp;token=93cb5aa7-801b-4391-84eb-5997fe1739b0" alt=""><figcaption></figcaption></figure>

### See Also

* [Quality Profiles](/product-guides/integral-zone/iz-suite/quality-control/profiles/quality-profiles.md)
* [Metric Profiles](/product-guides/integral-zone/iz-suite/quality-control/profiles/metric-profiles.md)
* [Quality Rules](/product-guides/integral-zone/iz-suite/quality-control/rules/quality-rules.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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/quality-control/rules/metric-rules.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.