> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.3/vizpads-explore/anomaly-management-for-line-charts/instance-level.md).

# Instance level

Configure how anomalies appear across your instance by enabling them in Search or Vizpads and setting a max anomaly limit to automatically control chart visibility.

Under **Settings -> Application Settings**, click on **Anomalies** in the left pane.

* **Display anomalies in Search** - If enabled, the anomalies will be displayed for charts in Search.
* **Display anomalies in Explore (Vizpads)** - If enabled, the anomalies will be displayed for charts in Vizpads.
* **Maximum number of anomalies to be displayed for a chart** - Provide the maximum number of anomalies to be displayed per chart (in Search and Vizpads). If the number of anomalies exceeds the threshold value specified in a chart, then the anomalies will be automatically hidden.

<figure><img src="https://content.gitbook.com/content/M1pa9Nct9EmVU4Ol8Mol/blobs/7IkwXCxyKXHdqP1JDne3/image.png" alt="" width="563"><figcaption><p>Anomaly settings</p></figcaption></figure>


---

# 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://help.tellius.com/tellius-6.3/vizpads-explore/anomaly-management-for-line-charts/instance-level.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.