> 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/observe-visibility-and-insights/unit-economics/analytics.md).

# Analytics

Analytics is where you read a published unit economics report. You can see cost per unit over time, group it by any column in the report, compare it with the usage behind it, and export the numbers.

Go to **Observe → Unit Economics → Analytics**.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2F4y6EZBkFXowjxXWyqWsM%2Fimage.png?alt=media&amp;token=f906cf7d-93c2-416d-9806-b0e3fbf55e93" alt=""><figcaption></figcaption></figure>

### Choose the report

| Control                    | What it does                                                   |
| -------------------------- | -------------------------------------------------------------- |
| Unit Cost Report           | Picks the report to view                                       |
| Report Version             | Picks the version. Earlier versions are marked Archived        |
| Default Report             | Switches saved views of this report                            |
| Date range and granularity | Sets the period and the interval, such as Last Month and Daily |
| Filters                    | Narrows the data with rules                                    |

### Read the chart and table

* **Metrics** lists the measures in the report, such as Cost and Database Size.
* **Group By** splits the data by a column in the report, such as customer.
* **Graph Metrics** picks which measure the chart shows.
* Switch between bar and line charts, or click **Hide Chart**.

The table shows a **Total** row, the total of each metric for the period, and each metric per day or month. Use **Export** to download it.

### Filter the report

Click **Filters** and add rules. Under **Show Results When**, choose whether all rules must match. For example, a rule of **Cost Source** in **AWS** shows only the cost that came from AWS.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FM6Wk4dwqOqkXMqWAHOsZ%2Fimage.png?alt=media&amp;token=d9565939-edba-430a-988a-28e0f370339e" alt=""><figcaption></figcaption></figure>


---

# 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/observe-visibility-and-insights/unit-economics/analytics.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.
