> For the complete documentation index, see [llms.txt](https://docs.euno.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.euno.ai/using-euno/usage-optimization/sigma-usage-data.md).

# Sigma Usage Data

Euno tracks warehouse workloads generated by Sigma resources to help teams understand cost drivers, identify frequently accessed content, and maintain a healthy BI environment.

{% hint style="info" %}
If you want user-level impression data from Sigma exports stored in S3 or GCS, see [Sigma Impressions Data](/using-euno/usage-optimization/sigma-impressions-data.md) and the [Sigma Impressions integration setup guide](/sources/business-intelligence/sigma-impressions-integration.md).
{% endhint %}

### **Warehouse Query Records (from your data warehouse)**

**Definition:**\
Read queries issued to the data warehouse as a result of users interacting with Sigma workbooks, and elements. When Sigma submits a query to the warehouse, it includes metadata that allows Euno to attribute the workload back to a specific Sigma resource.

**Source:**\
Warehouse query logs (e.g., Snowflake), provided that Sigma usage observation is enabled in your data-warehouse source configuration in Euno.

{% hint style="info" %}
This feature is currently supported only for Snowflake, with additional platforms planned for future releases.
{% endhint %}

| Property                                                                                                                                                    | Definition                                                                                                             | Applicable to                                                                                                               |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| <p><code>total\_read\_queries\_14d</code></p><p><code>total\_read\_queries\_30d</code></p><p><code>total\_read\_queries\_60d</code><br><br><br><br><br></p> | When integrated with a supported warehouse, the total read queries for the timeframe are propagated to the resource.   | <p><code>sigma\_workbook</code>, <code>sigma\_workbook\_element</code> ,</p><p><code>sigma\_data\_model\_element</code></p> |
| <p><code>total\_read\_credits\_14d</code></p><p><code>total\_read\_credits\_30d</code></p><p><code>total\_read\_credits\_60d</code></p>                     | <p>When integrated with Snowflake, the total read credits for the timeframe propagated to the resource.</p><p><br></p> | <p><code>sigma\_workbook</code>, <code>sigma\_workbook\_element</code> ,</p><p><code>sigma\_data\_model\_element</code></p> |
| <p><code>total\_read\_cost\_14d</code></p><p><code>total\_read\_cost\_30d</code></p><p><code>total\_read\_cost\_60d</code></p>                              | When integrated with Snowflake warehouse, the total read cost for the timeframe propagated to the resource.            | <p><code>sigma\_workbook</code>, <code>sigma\_workbook\_element</code> ,</p><p><code>sigma\_data\_model\_element</code></p> |


---

# 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.euno.ai/using-euno/usage-optimization/sigma-usage-data.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.