> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/govern-control-and-governance/budgets/budget-alerts.md).

# Budget Alerts

Budget alerts are Workflow triggers. Use them to send budget updates and warnings to Slack, email or any other Workflow action.

### Choose a budget trigger

1. Go to **Automate → Workflows** and create a workflow.
2. In **Select a trigger**, open the **Budget & Forecasting** category.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FrnyCBeG5GBogt2C2G1Fi%2Fimage.png?alt=media&amp;token=d2cf016e-15e9-41a4-93cc-8e1a456d0ebc" alt=""><figcaption></figcaption></figure>

| Trigger                       | Group                       | What it does                                                                                                                                                                                    |
| ----------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Budget Utilization Digest     | Budget & Forecasting Alerts | Sends a digest of how much of the budget has been used in the period                                                                                                                            |
| Budget pro-rata vs cost alert | Budget & Forecasting Alerts | Alerts when spend runs ahead of the budget for the period so far                                                                                                                                |
| Budget vs Forecast alert      | Budget & Forecasting Alerts | <\<CONFIRM = what Budget vs Forecast alert does>>                                                                                                                                               |
| Budget Performance AI Summary | Budget Reports              | Sends a monthly AI summary of cost against budget for the last 3 months, with anomalous resources, new resources and top contributors to leaks. Reports also appear on the Budget AI Report tab |

### Set up a pro-rata alert

The pro-rata budget is the part of the period's budget you would have spent by today if spending were even. On day 10 of a 30-day month, the pro-rata amount of a $30,000 monthly budget is $10,000.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FygILnCvuVen0Opso05zO%2Fimage.png?alt=media&amp;token=0a278676-d2af-4d28-babf-6634900ed8a5" alt=""><figcaption></figcaption></figure>

1. Add the **Budget pro-rata vs cost alert** trigger.
2. In **Select Budget Report**, choose the budget to monitor. **Budget Granularity**, **Budget Source** and **Cost Type** fill in from the budget.
3. Under **Alert Setup**, set one or both conditions:

   * **Cumulative costs exceed** a percentage of the pro-rata budget.
   * **If my costs exceed** a percentage of the full budget for the period.

   When you use both, choose **OR** to alert when either is met.
4. Choose the **Hour of the day** to run the check.
5. Add an action, such as **Send Slack alert to Users**, and click **Publish**.

**Example.** With 80% of pro-rata OR 90% of the monthly budget, a $30,000 monthly budget alerts on day 10 once cost passes $8,000 (80% of the $10,000 pro-rata amount). It also alerts at any point in the month once cost passes $27,000.


---

# 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://docs.onelens.cloud/govern-control-and-governance/budgets/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.
