> 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-5.6/feed/alerts-on-the-detection-of-anomalies.md). # Alerts on the detection of anomalies Feed sends out different alerts on detecting any anomalies Once a metric has been configured to track, Tellius checks for anomalies every time a Business View is refreshed. When an anomaly is detected in the metric being tracked, Tellius alerts the users concerned in the following ways: ### **In-app alert** A panel will be created on the Feed page with the following details. The Feed generated is fully dynamic, with which you can interact to get detailed insights into the "what" and "why" of the change.

* Details of the metric being tracked (name of the Feed, frequency of monitoring) * The change detected (drop/spike in the value) * Timestamp when the anomaly occurred * A line chart for the tracked metric * The **Details** button will redirect you to the associated Insight, where you can get additional details on what drove the change.

### **Email alert** An email will be sent to the creator and subscribers of the Feed. The email contains the details of the anomaly along with links to the generated Feed and associated objects. The following is a sample email:

--- # 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-5.6/feed/alerts-on-the-detection-of-anomalies.md?ask=&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.