> For the complete documentation index, see [llms.txt](https://docs.cloud-halo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud-halo.io/finops/anomaly-alerts.md). # Anomaly alerts Cloud Halo detects unusual spend patterns after sync and can notify teams when a medium or high anomaly appears. ## How anomalies work Anomaly detection compares recent daily spend against historical patterns. Anomalies can be caused by: * New services * Usage spikes * Batch jobs * Misconfigured resources * Billing adjustments * Seasonal or month-end patterns ## Notifications Anomaly alerts can be delivered by: * Email * Slack incoming webhook Use Slack for operational teams that already route infrastructure alerts to a shared channel. ## Acknowledge an anomaly Acknowledge an anomaly when your team has reviewed it and no longer needs it highlighted as new. Acknowledgement is useful for: * Confirming investigation ownership * Reducing repeated review work * Keeping the anomaly list focused ## Suppress an expected pattern Suppress an anomaly pattern when the spend change is expected for a known period. Add a suppression reason and an expiry date. Examples: * Monthly data processing run * Planned migration * Performance test window * Temporary customer project Suppression should be time-limited so unexpected future changes are still visible. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cloud-halo.io/finops/anomaly-alerts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.