> 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-performance.md).

# Budget Performance

Budget Performance shows how actual cost compares with budget, across all budgets and for each one in detail.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2F5GXB1OPbEjV2yxriRG7V%2Fimage.png?alt=media&amp;token=4d161322-ef25-418d-843b-f81eef83125b" alt=""><figcaption></figcaption></figure>

### Performance overview

Go to **Govern → Budgets** and open the **Budget Performance** tab.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FutuRsWCIIzXzWvZDbK51%2Fimage.png?alt=media&amp;token=c29098d3-1595-4a5f-bf90-c8e834834e8c" alt=""><figcaption></figcaption></figure>

Three cards sit at the top:

| Card             | What it counts                                                    |
| ---------------- | ----------------------------------------------------------------- |
| Budgets Created  | Budgets included in the performance view                          |
| Budgets On Track | Budgets where last month's cost stayed within last month's budget |
| Budgets Leaked   | Budgets where last month's cost went over last month's budget     |

The table lists each budget with:

| Column              | What it shows                                               |
| ------------------- | ----------------------------------------------------------- |
| Budget (Last Month) | The amount budgeted for last month                          |
| Cost (Last Month)   | Actual cost for last month                                  |
| Delta               | Cost minus budget. Red means over budget, green means under |
| Delta %             | Delta as a percentage of the budget                         |

For example, a budget of $4,014.00 with a cost of $5,587.67 shows a Delta of $1,573.67 and a Delta % of 39.20%, and counts as leaked.

### Drill into a budget

Click the chart icon at the end of a row to open that budget's performance in detail.

<\<SS = budget-performance-drilldown>>

Use the date range and granularity selectors at the top right to change the period.

The cards at the top show:

* **Current Cost** for the selected range.
* **Total Budget** for the selected range.
* **Cost vs Budget Performance**, which is current cost minus total budget. A negative number means you have spent less than budgeted.

The table has one row per value of the budget's dimension, plus a **COST** total row at the top. For each row you see:

* **Total Budget**, **Total Cost** and **Budget Utilization** (cost as a percentage of budget) for the whole range.
* **Budget**, **Cost** and **Budget Utilized** for each period. Values over 100% show in red.

> A row with a $0 budget and some cost shows a utilization of 999%.

Use **Export** to download the table.

### See budgets in Cost Atlas

You can also view a budget on top of its Report in Cost Atlas.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FeZLywSZcEs2y76FbieK6%2Fimage.png?alt=media&amp;token=91dce079-48e2-4ac1-9496-3e5a643139b1" alt=""><figcaption></figcaption></figure>

1. Open the budget's Report in **Cost Atlas**.
2. Click the budget icon in the toolbar.
3. Turn on **Show Budget**. The chart shows the budget as a dashed line, and the table adds Budget, Cost and Budget Utilized columns for each period.
4. Optional. Turn on **Only Show Overruns** to focus on the rows that went over budget.

   <\<CONFIRM = exact behaviour of Only Show Overruns>>
5. Above the table, switch **Show** between **Budget Utilized %** and **Budget Leftover $**.

Click **Manage Budget** in the same menu to open the budget.

### Budget AI Report

The **Budget AI Report** tab collects every report generated by the **Budget Performance AI Summary** workflow, so you can read past reports in one place instead of searching email.

Each report summarises cost against budget for the last 3 months and groups the drivers behind a budget leak into three categories:

| Driver              | What it shows                                          |
| ------------------- | ------------------------------------------------------ |
| Anomalous resources | Resources whose cost spiked above their normal pattern |
| New resources       | Resources created during the period that added cost    |
| Top contributors    | The resources that added the most to the overrun       |

To start receiving these reports, set up the Budget Performance AI Summary trigger. See Budget Alerts.


---

# 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-performance.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.
