> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/pump-view/anomalies-and-budget-alerts.md).

# Anomalies

Learn how Pump automatically detects unusual cloud spend and alerts you.

Anomaly Alerts notify you when Pump detects unusual spend patterns across your connected providers. Unlike budgets (which require you to define a target), anomaly detection works automatically based on your historical spend data.

When Pump identifies a significant deviation from expected spend, it sends an alert to your configured channels. The alert includes the affected service or account, the magnitude of the change, and a link to investigate in the Playground.

{% embed url="<https://youtu.be/xcjM5BHPa6Q>" %}

## Configuring anomaly alerts

Anomaly alert settings are available under [**Organization settings > Notifications**](https://app.pump.co/settings#notifications). You can configure which channels receive anomaly notifications (email, Slack, or both).

## Investigating an anomaly

When you receive an anomaly alert:

1. Click the link in the notification to open the relevant time range in the Playground.
2. Use the [**Top Movers**](https://app.pump.co/view/reports) view to identify which services or accounts drove the change.
3. Add an Annotation to document what caused the anomaly for future reference.

## Budget Alerts vs. Anomaly Alerts

|                | Budget Alerts                                                   | Anomaly Alerts                                                  |
| -------------- | --------------------------------------------------------------- | --------------------------------------------------------------- |
| Trigger        | You define a dollar threshold                                   | Pump detects deviations from expected patterns                  |
| Best for       | Known cost targets (e.g., "don't exceed $50K/month on compute") | Catching unexpected changes you would not have set a budget for |
| Setup required | Create a budget with scope and thresholds                       | Minimal. Configure notification channels.                       |
| Scope          | Scoped to specific accounts and/or services                     | Across all connected providers                                  |

Both alert types can be delivered to email and Slack. Using both together gives you coverage for planned limits and unplanned surprises. To set up budgets, see [Budget Alerts](https://help.pump.co/pump-view/budget-alerts.md).


---

# 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.pump.co/pump-view/anomalies-and-budget-alerts.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.
