Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Ftco-optimizer%2Fusage-overview-and-statistics.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Faccount-management%2Ftco-optimizer%2Fusage-overview-and-statistics.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# Usage overview and statistics

## Usage overview[​](#usage-overview "Direct link to Usage overview")

Use the **Overview** page to understand how your daily quota is consumed across priorities and how routing affects cost. Select **Overview** in the TCO Optimizer's left navigation.

[![The TCO Optimizer Overview page with the Daily team quota, Daily quota left, Data blocked today, and Yearly savings cards, the Usage by priority chart, per-data-type charts, and the Feature set by priority table](/docs/assets/images/tco_optimizer_overview-e198b950f67947fcd4d4d3938dd19bd6.webp)](https://coralogix.com/docs/assets/images/tco_optimizer_overview-e198b950f67947fcd4d4d3938dd19bd6.webp)

The page includes:

### Daily team quota[​](#daily-team-quota "Direct link to Daily team quota")

Shows your available daily unit quota. Coralogix uses a unit-based pricing model, where a unit is a universal billing metric per observability pillar.

### Daily quota left[​](#daily-quota-left "Direct link to Daily quota left")

Shows how many units remain of your daily quota, with a progress bar and the percentage used. The quota resets daily.

### Data blocked today[​](#data-blocked-today "Direct link to Data blocked today")

Shows how much data your policies blocked today, in GB, and what share of your ingest that is.

### Yearly savings[​](#yearly-savings "Direct link to Yearly savings")

Shows the estimated yearly saving as a percentage of your quota, from routing data to Medium (Monitoring) and Low (Compliance) instead of High (Frequent Search).

### Usage by priority[​](#usage-by-priority "Direct link to Usage by priority")

A stacked bar chart of daily usage over the last seven days, split by **High**, **Medium**, **Low**, and **Block**.

### Usage per data type[​](#usage-per-data-type "Direct link to Usage per data type")

A chart for each of **Logs**, **Traces**, and **RUM** shows how that data type's usage is split across priorities.

### Feature set by priority[​](#feature-set-by-priority "Direct link to Feature set by priority")

A table of what each priority includes, with a tab for **Logs**, **Traces**, and **RUM**. Each row is a feature with a description and a check mark under every priority that supports it. The **Learn more** link opens [Features by priority level](https://coralogix.com/docs/user-guides/account-management/tco-optimizer.md#features-by-priority-level).

Use the Overview to quickly assess quota consumption, validate the impact of your TCO policies, and identify opportunities for further cost optimization.

## Statistics[​](#statistics "Direct link to Statistics")

Statistics show ingested logs, traces, or RUM events organized by key dimensions and their contribution to usage. Use this view to identify high-volume data and turn it into policies. Statistics are an aggregate over the time range you select, **Last 24 hours** or **Last 7 days**. To see which priority a quota-based policy is in right now, see [Live policy status](https://coralogix.com/docs/user-guides/account-management/tco-optimizer/create-and-manage-policies.md#live-policy-status).

[![The Logs Statistics view with the Filtered by control, the Last 24 hours and Last 7 days toggle, Group by, Search, and a grid with a checkbox column and the Application, Subsystem, Severity, Affecting policy, Priority, Destination, % Quota, Data sent, and Units columns](/docs/assets/images/log-statistics-destination-99c6e8448c1d681704011fe5084f596d.webp)](https://coralogix.com/docs/assets/images/log-statistics-destination-99c6e8448c1d681704011fe5084f596d.webp)

Note

The **Destination** column is available on the **Logs** tab. RUM statistics do not include it, because RUM policies always route to `default/rum.events`.

Use this view to:

* Group by `application`, `subsystem`, `severity`, `affecting policy`, and `priority`
* Expand an application to see its subsystems, then expand a subsystem to see its severity breakdown
* See the **Destination** each combination is routed to, alongside its **Affecting policy** and **Priority**
* See contribution to **% Quota**, **Data sent**, and **Units (U)** for each combination
* Validate expected impact before saving

### Row menu actions[​](#row-menu-actions "Direct link to Row menu actions")

* **Add rule**: Pre-fills the policy form with the row's values
* **Drill into logs**: Opens a query filtered to the row's values
* **Copy as filter**: Copies application, subsystem, and severity chips for reuse

### Slice and filter the data[​](#slice-and-filter-the-data "Direct link to Slice and filter the data")

* **Group by chips**: Choose which fields to include in the breakdown. Drag and drop chips to rearrange them.
* **Filtered by**: Add filters to narrow the rows.
* **Search**: Filter rows by application, subsystem, severity, or priority (supports partial matches).
* **Include/exclude values**: Use chip menus to add or remove specific values.
* **Reset**: Clear temporary filters and return to the default settings.

### Create a policy from statistics[​](#create-a-policy-from-statistics "Direct link to Create a policy from statistics")

Turn any selection into a policy without leaving the page:

1. Select a row. The **Create policy** button is inactive until you do.
2. Choose **Add rule**. The **Create policy** form opens with the Builder pre-filled.
3. Choose a priority: High (Frequent Search), Medium (Monitoring), Low (Compliance), or Blocked.
4. (Optional) Set archive retention.
5. Review the **Preview** panel for data sent, % quota, and units impact.
6. Toggle **Enable policy** on to activate immediately.
7. Select **Create**.

The new policy appears in the TCO rules table. Order matters. Set **Policy order** to place it **First** (highest precedence) or **Last**.

### Understand the "affecting policy" column[​](#understand-the-affecting-policy-column "Direct link to Understand the \"affecting policy\" column")

When a combination already matches a policy, the **Affecting policy** column displays the policy currently in effect.

Use it to:

* Avoid creating duplicate policies
* Spot combinations that fall into the default High (Frequent Search) priority (shown as **No policy**)
* Decide whether to edit an existing policy or add a higher-precedence one