Data usage
Data Usage is superseded by Usage and quota, which combines it with Quota Manager on a single page. The navigation entry now reads Data Usage (Legacy) and opens the new page.
Coralogix provides clear, flexible, and detailed insights into your observability data usage. Whether you manage logs, metrics, traces, or AI usage, consumption is measured in units. A consistent billing metric that gives you control over your data volume, cost, and performance.
This guide explains how Coralogix calculates, monitors, and reports data usage. Learn how to interpret usage statistics, understand your billing model, and use the Data Usage interface and reports to optimize your account.
Understand the unit-based pricing model
Coralogix employs a unit-based pricing model for its observability features.
A unit serves as a universal billing metric per entity type.
Entity types act as data types and objects across the Coralogix platform, breaking down observability pillars into more granular units.
| Pillar | Example entity types | Description |
|---|---|---|
| Logs | Browser logs, alerts | Event data from applications or user interactions |
| Metrics | Metrics | Numeric measurements of system performance |
| Traces | Spans | Detailed traces of operations and transactions |
| Binary | Session recordings, Source maps | Large binary objects, e.g., recordings or debug files |
| Profiles | CPU profiles | Continuous profiling data for performance analysis |
| AI | Olly, Evals, Guardrails | Per-user AI usage (Olly) and AI Center evaluations and guardrails. All AI features are billed in AI Units. See AI Units pricing. |
Ingested data flows through several TCO pipelines. Each pipeline’s TCO priority determines its unit cost. If no priority is assigned, the data is treated as high priority.
Usage is measured against your daily unit quota.
User data sent
User-defined datasets
Data routed to user-defined datasets counts toward your daily unit quota. Usage is tracked per dataset and per dataspace, so you can see how much each dataset consumes across the default/ dataspace.
The unit cost depends on the TCO priority of the routing policy applied to that dataset. The same rates as standard logs apply:
| Pipeline | Sent data | Units |
|---|---|---|
| Medium priority | 1 GB | 0.32 |
| Low priority | 1 GB | 0.12 |
High and Block priorities are available for default/logs only. User-defined datasets do not support High or Block routing.
Dataset-level usage appears under the User selection on the CX units tab. Use the Slice and filter controls and select dataset as a breakdown field to see usage per dataset.
Logs
| Pipeline | Sent data | Units |
|---|---|---|
| High priority | 1 GB | 0.75 |
| Medium priority | 1 GB | 0.32 |
| Low priority | 1 GB | 0.12 |
| Blocked logs | 1 GB | 0.08 |
Metrics
| Pipeline | Sent data | Units |
|---|---|---|
| Metrics | 30 GB | 1 |
Traces
| Pipeline | Sent data | Units |
|---|---|---|
| High priority | 1 GB | 0.5 |
| Medium priority | 1 GB | 0.25 |
| Low priority | 1 GB | 0.1 |
1 unit = $1.50 of usage for logs, metrics, or traces in any pipeline.
System data sent
System data contains Coralogix-generated metadata related to your environment. When enabled, this data counts toward your daily quota.
Learn more about System datasets.
Infrastructure
Infrastructure events are telemetry signals collected from your cloud and Kubernetes environments, such as node statuses, pod lifecycle events, and configuration metadata. These are used to populate Infrastructure Explorer.
Blocked infrastructure events are those dropped before ingestion, usually due to namespace filters (e.g., excluding kube-system) or fair usage constraints.
| Pipeline | Sent data | Units |
|---|---|---|
| Infrastructure events | Any volume | 0 |
Learn more about Infrastructure Explorer.
AI Units
The AI Units tab tracks consumption for all AI-powered features (Olly, Olly Mini, and AI Center evaluations and guardrails) in one place. All AI features are billed in AI Units at per-model, per-token rates. Olly and Olly Mini bill per user; AI Center evaluations and guardrails bill per team.
For full rates and worked examples, see AI Units pricing.
The tab has three stacked sections:
- Total: combined daily AI Units consumption across per-user and AI Center usage
- Olly: per-user breakdown for Olly and Olly Mini usage: total units, monthly limit, max/min/avg daily, the daily usage chart, and the per-user Units breakdown table. The breakdown attributes usage by Identity Type (human users (by username) and API keys or automations (by key name)) so you can see exactly which callers consumed units. Free teams also see a free-tier banner here.
- AI Center: policy-level breakdown for evaluations and guardrails. Policy names include their type (for example, Toxicity (Eval) or Prompt Injection (Guardrail)) so you can distinguish between them at a glance.
Each section can be collapsed independently.
Two admin controls apply:
- Team-wide limit: use Quota Rules to cap the team's total AI Units consumption on the
ollyentity type. - Per-user and automation limits: use Olly usage management to cap individual users and automations.
Monitor usage
The Usage & Quota page shows real-time unit consumption across your Coralogix account.
Select Settings, then Usage & Quota under Subscriptions.
Time picker
Data Usage supports a full dynamic time selector, so you can choose a preset or set a custom date and time range to view and compare usage across any timeframe. This makes it easier to investigate spikes and anomalies in the exact period that matters and run accurate period-over-period comparisons for cost and quota planning.
To select a preset or custom time range for usage:
-
Open the time selector.
-
Choose a preset, or select Custom and set a date/time range.
-
Select Apply.
Visualizations and totals update for the selected period.
Usage tabs
The page has two tabs, each showing how much of its allowance you have used against the total. A selector above the chart narrows the tab to one source.
CX units covers your ingested data and is measured against a daily quota.
| Selection | Covers |
|---|---|
| Total CX units | Every source below combined. The default. |
| User | User-generated data, including user-defined datasets |
| System | System-generated data, such as alert history, audit events, and schema metadata |
| Infrastructure | Infrastructure events |
AI Units covers AI consumption and is measured against a monthly quota, so its cards report the month to date rather than the day.
| Selection | Covers |
|---|---|
| Total AI units | Olly and AI Center combined. The default. |
| Olly | Olly usage, charged per user |
| AI Center | Evaluations and guardrails |
Usage statistics
Each tab displays a row of counter cards summarizing consumption over the selected period. Cards vary by tab, and quota-scoped tabs show additional cards that put usage in context against the quota.
CX units
| Card | Description |
|---|---|
| Daily quota left | Units remaining today, against your allocated daily quota, with the percentage used. Resets daily. |
| Daily quota | Your team's allocated daily unit quota |
| Blocked days | Number of days with blocked data due to quota limits |
| Blocked units (est.) | Estimated units blocked due to quota limits |
| Max daily usage | Highest daily ingested volume, with a trend badge |
| Min daily usage | Lowest daily ingested volume, with a trend badge |
| Avg daily usage | Average daily ingested volume, with a trend badge |
| PAYG usage total | Total pay-as-you-go usage in the selected period. Shows an Off badge when pay-as-you-go is not enabled. |
AI Units
The AI quota is monthly rather than daily, so the first card reports the month to date and names the day you are on.
| Card | Description |
|---|---|
| Monthly quota left | Units remaining this month, against your allocated monthly quota, with the percentage used and which day of the month it is |
| Blocked days | Number of days with blocked data due to quota limits |
| Blocked units (est.) | Estimated units blocked due to quota limits |
| Max daily usage | Highest daily usage, with a trend badge |
| Min daily usage | Lowest daily usage, with a trend badge |
| Avg daily usage | Average daily usage, with a trend badge |
Trend badges
The Max daily usage, Min daily usage, and Avg daily usage cards display a trend badge that compares the second half of the selected period to the first half. An upward arrow indicates the value increased; a downward arrow indicates it decreased. The percentage shows the relative change between the two halves, helping you spot rising or declining usage at a glance.
Hover over any card label to see a tooltip with a short description of the metric.
Units per entity type
Hover over columns in the bar chart to view unit distribution by day, or scroll to the breakdown grid for detailed totals by entity type.
Units breakdown
Each entity type shows:
- Total units and percentage of total usage
- Volume of ingested data
Slice and filter the data
Choose fields (e.g., pillar, entity type, TCO priority, dataset, dataspace) to include in the breakdown. Drag chips to rearrange them.
More actions
The more actions menu in the Usage & Quota header carries four items:
| Item | What it does |
|---|---|
| View usage overview | Returns to the overview cards and chart |
| View Data Usage Dashboard | Opens the Data Usage dashboard from the Coralogix System Monitoring extension, which charts the data usage metrics |
| Hide usage annotations | Removes annotations from the usage chart |
| Generate report | Opens the export panel |
Enhance observability with data usage metrics
Enable Data Usage Metrics to view real-time usage patterns. Build dashboards, set alerts, and generate summaries.
You can toggle metrics ingestion and the dataplan.usage_events system dataset from the Data Usage settings panel.
Generate and export usage reports
Generate custom usage reports directly from the Usage & Quota page. Configure the file name, date range, scope, format, and report type to match your analysis or audit workflow.
To open the export panel, select the more actions menu in the Usage & Quota header, then Generate report.
Choose a report type
The Generate report drawer opens with a Report type selector:
- Data Usage Report: the standard usage export. It exports usage metrics by data pillar, application, or subsystem, and is the default.
- Pay-as-you-go report: a per-day export of your pay-as-you-go (overage) unit consumption. This option appears only for teams with pay-as-you-go enabled. See Pay-as-you-go report.
Selecting a different report type replaces the form in place with that report's fields. Switching back restores each report's configuration without closing the drawer.
Configure the report
The following options apply to the Data Usage Report type.
| Field | Description |
|---|---|
| File name | Editable base name for the exported file. The default follows data-usage-[scope]-[from_date]_[to_date]-[timestamp], and regenerates as you change the scope or date range until you edit the value manually. |
| Date range | Preset window for the report: Current month, Last 30 days, or Last 90 days. The maximum range is 90 days. |
| Tabs | One or more tabs to include, selected as chips. The tabs offered mirror those on the Usage & Quota page, so CX units, AI Units, or both. Some tabs depend on your plan or enabled features, and the available tabs also depend on the selected report type. |
| Export as | File format: CSV, TSV, or JSON. |
| Include headers | Adds column names as the first row of the exported file. Available for CSV and TSV formats only. |
| Type | Overview report or Detailed report. See the sections below. |
| Apply filters | Applies the current Data Usage table filters and grouping to the exported data. Available for Overview reports when a single tab is selected. |
Overview and detailed reports
Overview report
Exports the summarized metrics visible on each selected tab, including total usage, daily max, and quota usage for the selected date range. Overview reports support the Apply filters option, which carries over the filters and grouping configuration from the Usage & Quota page.
Overview exports support the CX units and AI Units tabs.
Detailed report
Exports the full daily breakdown per entity type or data pillar, including all available metrics. Detailed reports include the full daily breakdown with no row limit.
Detailed exports support the CX units and AI Units tabs.
Export formats and bundling
- A single-tab export produces one file in the chosen format.
- A multi-tab CSV or TSV export bundles one file per tab into a
.ziparchive. - A multi-tab JSON export produces a single hierarchical JSON file containing each tab as a nested object.
CSV and TSV columns
CSV and TSV exports include the following columns, depending on the selected tab:
- Date
- Application
- Subsystem
- TCO priority
- Entity type
- Dataset
- Dataspace
- Ingested data (GB sent)
- Unit consumption
Pay-as-you-go report
A Pay-as-you-go report exports your pay-as-you-go (overage) unit consumption, the usage billed above your daily quota. The report type appears in the Report type selector only for teams that have pay-as-you-go enabled.
Pay-as-you-go usage is calculated against your team quota pool as a single daily total, so the report has no entity-type, priority, or pillar breakdown. When you select Pay-as-you-go report, the drawer shows these fields:
| Field | Description |
|---|---|
| File name | Editable base name for the exported file, pre-filled from the selected date range. |
| Date range | The period to export. |
| Export as | File format: CSV, TSV, or JSON. |
| Include headers | Adds column names as the first row of the exported file. Available for CSV and TSV formats only. |
| Type | Overview report or Detailed report. A detailed report lists per-day pay-as-you-go units (date and units), with no entity, priority, or pillar columns. |
The exported values reconcile with the PAYG usage total shown on the Data Usage page for the same date range.
Data Usage Service API
Reports are also available programmatically through the Data Usage Service API.
Permissions
To access Data Usage, the following permissions are required:
| Resource | Action | Description |
|---|---|---|
data-usage | manage | Manage Data Usage |
data-usage | read | View Data Usage |