--- title: Usage overview and statistics description: Track how your daily quota is consumed across priorities in the TCO Optimizer Overview, and use Statistics to turn high-volume data into policies. url: https://coralogix.com/docs/user-guides/account-management/tco-optimizer/usage-overview-and-statistics/ product: dataengine feature: TCO Optimizer feature_id: tco-optimizer feature_identifier: dataengine/tco-optimizer last_updated: '2026-10-22' --- # Usage overview and statistics ## 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 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 Shows how many units remain of your daily quota, with a progress bar and the percentage used. The quota resets daily. ### Data blocked today Shows how much data your policies blocked today, in GB, and what share of your ingest that is. ### 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 A stacked bar chart of daily usage over the last seven days, split by **High**, **Medium**, **Low**, and **Block**. ### 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 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 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 grouped by Severity, with the Last 24 hours and Last 7 days toggle, the Group by control with a Severity chip, the search box, and a grid with expandable severity rows and the Severity, Application, Subsystem, Affecting policy, Priority, Destination, % Quota, Data sent, and Units columns](/docs/assets/images/log-statistics-group-by-06774c3825c4a5326c2d3111a9d93e87.webp)](https://coralogix.com/docs/assets/images/log-statistics-group-by-06774c3825c4a5326c2d3111a9d93e87.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 a group to see the rows inside it * 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 * **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 * **Group by**: Select **+** to choose one or more fields, **Application**, **Subsystem**, **Severity**, **AffectingPolicy**, **Priority**, and on the **Logs** page **Destination**, and select **Apply**. Each field shows as a chip, and the grid groups its rows by those fields, with an expand arrow on each group. While rows are grouped, the **⋮** menu next to the search box offers **Expand all** and **Collapse all**. Remove a field with the **x** on its chip, or clear every field to return to the ungrouped list. * **Filters**: Use the **Filters** section in the left navigation to narrow the rows. The same filters apply to the data type's policies. See [Filter the policy list](https://coralogix.com/docs/user-guides/account-management/tco-optimizer/create-and-manage-policies.md#filter-the-policy-list). * **Search**: Filter rows by application, subsystem, severity, or priority (supports partial matches). * **Include/exclude values**: Use chip menus to add or remove specific values. ### 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 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