> 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-documentation/feed.md). # Feed - [What is a Feed in Tellius?](https://help.tellius.com/tellius-documentation/feed/what-is-a-feed-in-tellius.md): Learn what a Feed is in Tellius—monitor key metrics in real time and get alerts for spikes, drops, or anomalies without constantly checking dashboards. - [Alerts on the detection of anomalies](https://help.tellius.com/tellius-documentation/feed/alerts-on-the-detection-of-anomalies.md): Tellius Feed flags anomalies at refresh, with in-app panels, timestamps, charts, and ‘Details’ to Insights—plus email alerts to creators and subscribers. - [Actions done on a tracking Feed](https://help.tellius.com/tellius-documentation/feed/actions-done-on-a-tracking-feed.md): Manage your tracking Feeds by viewing, editing, sharing, pinning, or deleting metrics. See all Feed details in one place and keep key KPIs easy to monitor. - [Track a new metric](https://help.tellius.com/tellius-documentation/feed/track-a-new-metric.md): Track metrics over time, set smart or threshold-based conditions, and get automated Feed alerts with insights, breakdowns, and scheduled email notifications. --- # 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-documentation/feed.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.