> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/ibcs-user-guide/ibcs/negative-metrics.md).

# Negative Metrics

<br>

#### Mapping metrics as negative <a href="#mapping-metrics-as-negative" id="mapping-metrics-as-negative"></a>

By default, all metrics are regarded as positive; that is, any positive change in the metric value (increase) is regarded as ‘good’ and is depicted in green (the default color). Obviously, there are some metrics (such as expenses) where a rise should be viewed negatively. These metrics should be labelled as such in the setting. This setup is currently done in the IBCSglobal.txt file.

\
The relevant section of the file looks like this:

```
#Support for negative metrics. Add metric names separated by comma
#negativeMetrics=AC
```

To add new metric names that should be viewed negatively,

* Remove the leading # mark from the line (the # mark turns the line into a comment, which means it will not be read for system configuration purposes). The line now appears to be

  ```
  #Support for negative metrics. Add metric names separated by comma
  negativeMetrics=AC
  ```
* add any name of the metric or a pattern (regular expression)
* each name and pattern should be separated by a comma
* while using regular expressions, the entire expression should be enclosed with \[].

For example, if you would like to indicate that all metrics with the phrase expense in them should be treated as ‘negative’, you will change the line to

```
#Support for negative metrics. Add metric names separated by comma
negativeMetrics=[.*expense.*]
```

If you would like to add a specific metric name like ‘miscellaneous costs’, the line would now be

```
#Support for negative metrics. Add metric names separated by comma
negativeMetrics=[.*expense.*], miscellaneous costs
```


---

# 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.vitaracharts.com/ibcs-user-guide/ibcs/negative-metrics.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.