> For the complete documentation index, see [llms.txt](https://docs.opsnow.io/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/opsnow-user-guide-v0.2/menu/finops-kpis/history-tab.md).

# History Tab

The History tab serves as a comprehensive log for all activities and generated reports related to the FinOps KPI feature. It is designed to provide a complete audit trail, allowing you to track past performance reports and review configuration changes over time. The tab is divided into two main sections.

* **Report Tab:** The Report section displays each group's monthly KPI checklist. This allows teams to review their cloud performance based on predefined FinOps KPI standards and explore areas for improvement.
* **Audit Log Tab:** The Audit Log records all configuration changes related to KPI settings in chronological order. It is designed to transparently track all updates, including changes to targets, templates, and group member configurations.


---

# 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/opsnow-user-guide-v0.2/menu/finops-kpis/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.