# Snowflake Usage Data

## Table Activities in Euno

For resources of type **table** and for **supported sources** (currently only Snowflake), Euno displays key usage and cost insights derived from Snowflake's query history, if made available to Euno (see the [*Snowflake*](/sources/data-warehouses/snowflake-integration.md) configuration section for details).

#### Usage Categories

**1. Table Read**

* Total number of SELECT queries
* Cumulative query runtime (in hours/minutes)
* Total read credits consumed (if available)
* Estimated $ cost (if credits are mappable to $)

[list of read properties](/sources/data-warehouses/snowflake-integration/snowflake-integration-discovered-resources.md#read-properties)

**2. Table Write**

* Total number of DML queries (INSERT, UPDATE, DELETE, MERGE)
* Total number of materialized view refresh operations triggered by this table
* Cumulative write-related runtime
* Total compute credits consumed (if available)
* Estimated $ cost

[list of write properties](/sources/data-warehouses/snowflake-integration/snowflake-integration-discovered-resources.md#write-properties)

**3. Estimated Storage**

* Current table volume (compressed GB/TB)
* Projected storage cost for the selected time window (based on volume × $/TB/month rate)

[list of storage properties](/sources/data-warehouses/snowflake-integration/snowflake-integration-discovered-resources.md#storage-properties)

{% hint style="warning" %}
Snowflake usage metrics appear only when Euno can observe usable Snowflake usage history. If that history is unavailable or yields no usable usage events, these fields may remain empty (`null`) instead of showing `0`.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.euno.ai/using-euno/usage-optimization/snowflake-usage-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.