Skip to content

Data Usage

Coralogix provides clear, flexible, and detailed insights into your observability data usage. Whether you manage logs, metrics, traces, or AI evaluations, usage 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.

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.
PillarExample entity typesDescription
LogsBrowser logs, alertsEvent data from applications or user interactions
MetricsMetricsNumeric measurements of system performance
TracesSpansDetailed traces of operations and transactions
BinarySession recordings, Source mapsLarge binary objects, e.g., recordings or debug files
ProfilesCPU profilesContinuous profiling data for performance analysis

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

Logs

PipelineSent dataUnits
High priority1 GB0.75
Medium priority1 GB0.32
Low priority1 GB0.12
Blocked logs1 GB0.065

Blocked data counts as 8% of its original size to account for network ingestion overhead.

Metrics

PipelineSent dataUnits
Metrics30 GB1

Traces

PipelineSent dataUnits
High priority1 GB0.5
Medium priority1 GB0.25
Low priority1 GB0.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.
PipelineSent dataUnits
Infrastructure eventsAny volume0

Learn more about Infrastructure Explorer.

AI evaluators

AI evaluators assess LLM performance as part of Coralogix’s AI observability suite. Their usage is based on token volume and processing complexity.

  1. Tokens**: All input text is measured in tokens (words or symbols).
  2. Activated evaluators: Each evaluator adds a layer of analysis. Multiple evaluators may run simultaneously.
  3. Usage formula:
Units = (tokens × activated evaluators) / 1,000,000

AI pricing example

If an AI agent processes 10,000 tokens using 5 evaluators:

(10,000 × 5) / 1,000,000 = 0.05 units

Monitor usage in the interface

The Data Usage interface shows real-time unit consumption across your Coralogix account.

Navigate to Settings, then Data Usage.

Time picker

Select a time range for usage:

  • Current month (default)
  • Last 30 days
  • Last 90 days
  • Last 365 days

Usage tabs

The interface has five tabs:

  • User data: Total ingested user-generated data
  • System data: Total system-generated data, such as alert history, audit events, and schema metadata
  • AI tokens: Units consumed by LLM evaluations
  • Infra: Infrastructure events
  • Quota units: Daily unit consumption

Usage statistics

Each tab shows three metrics:

  • Total: Total billing units consumed during the selected date range
  • Daily max: Peak unit usage on any single day
  • Max saved quota: Units saved via TCO optimization

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) to include in the breakdown. Drag chips to rearrange them.

Enhance observability with Data Usage Metrics

Enable Data Usage Metrics to view real-time usage patterns. Build dashboards, set alerts, and generate summaries.

Generate and export usage reports

Standard data usage report

View unit consumption and ingested data for the past 90 days.

Detailed data usage report

View all ingested data by pipeline for the current month, past 30 days, or past 90 days. Reports show policy-level, day-by-day ingestion by entity type and TCO priority. Reports are available in the interface or via the Data Usage Service API.

CSV exports include:

  • Date
  • Application
  • Subsystem
  • TCO priority
  • Entity type
  • Ingested data (GB sent)
  • Unit consumption

Permissions

To access Data Usage, the following permissions are required:
ResourceActionDescription
data-usagemanageManage Data Usage
data-usagereadView Data Usage

Was this helpful?