> For the complete documentation index, see [llms.txt](https://docs.opsnow.io/dev-opsnow-user-guide-v0.2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsnow.io/dev-opsnow-user-guide-v0.2/menu/budgets/history-tab.md).

# History Tab

In **'History'**, you can view the notification delivery records, including when and under what conditions budget usage was detected, and which channels the alerts were sent through.

<figure><img src="/files/MHJ4K4iA8jVNwWNby3en" alt=""><figcaption></figcaption></figure>

1. **Date Range Filter:** Located in the upper-right corner, this filter allows you to set the time period for the notification records you want to view.
2. **Search Bar:** You can use this search bar to find specific notification records by entering keywords, such as a budget name, group, or recipient.
3. **Table:** This table provides a detailed log of all sent alerts. You can check records for the set period, including:&#x20;
   * **Sent Date:** The timestamp (date and time) when the notification was dispatched.
   * **Budget Name:** The identifier of the specific budget that triggered the alert.
   * **Budget Group:** The defined group to which the budget is assigned.
   * **Period:** The budget's configured time cycle (e.g., Monthly, Quarterly).
   * **Threshold:** The specific condition (e.g., percentage over or under) that was met to trigger the notification.
   * **Cloud Service Provider (CSP):** The cloud environment being monitored by the budget.
   * **Alert Channel:** The configured delivery method for the notification.
   * **Recipient:** The designated user or group that received the notification.
4. **Download Report:** This icon allows the user to download a detailed report that contains the budget information.

\ <br>


---

# 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.opsnow.io/dev-opsnow-user-guide-v0.2/menu/budgets/history-tab.md?ask=<question>&goal=<endgoal>
```

`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.