> 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/redshift-usage-data.md).

# Redshift Usage Data

> **Private preview:** The Redshift integration is currently in private preview. To enable it for your account, please contact support.

## Table Activities in Euno

For resources of type **table** from a **Redshift** source, Euno displays usage and cost insights derived from Redshift query history when **Extract Usage Metrics** is enabled. See the [Redshift](/sources/data-warehouses/redshift-integration.md) configuration section for setup and permissions.

Column resources receive read counts and distinct-user counts when **Extract Column Usage** is also enabled.

#### Usage Categories

**1. Table Read**

* Total number of read queries
* Cumulative query runtime
* Bytes processed
* Distinct users
* Estimated $ cost (when rates are configured)

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

**2. Table Write**

* DML, CTAS, COPY, and materialized view refresh operations on base tables and materialized views
* Cumulative write-related runtime, bytes, and cost
* Views and Spectrum external tables do not receive write metrics

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

**3. Estimated Storage**

* Current table volume
* Projected storage cost when a storage rate is configured

Spectrum external tables do not receive `row_count` / `volume`. Scan totals from S3 may appear from query history when usage is enabled.

{% hint style="info" %}
Redshift's detailed system logs retain about seven days. Euno accumulates a running query-history window across crawls. A 14-, 30-, or 60-day property stays empty (`null`) until that many days have been accumulated. Partial windows are not published as complete totals, and `0` is not used as a stand-in for "not enough history yet."
{% endhint %}


---

# 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/redshift-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.