Data Usage
View processed data and retention usage for your project.
Data Usage lets you monitor your project's data consumption across traces, spans, online evaluations, and test runs. Use this page to understand your usage patterns and track progress toward your plan limits.
Overview
The Overview tab provides a breakdown of usage by data type over a selected time period.
Usage Summary
Usage is broken down into five categories:
| Data Type | Description | Billing |
|---|---|---|
| Traces | Top-level observability units representing complete interactions | Contributes to GB usage |
| Spans | Individual operations within traces | Contributes to GB usage |
| Online Evals (metric data) | Evaluations run on production traces, spans, and threads | Counted separately |
| Test Runs | Evaluation runs from experiments and test suites | Counted separately |
| Signals | Classifier runs on traces and idle threads | Counted separately |
The summary shows:
- Total in period — Total data size and unit count for the selected time range
- Average per month — Average monthly data size and unit count
Ingested Trace/Span Data
This section shows your observability data ingestion over time. Your observability data usage is calculated based on GB-months—the total gigabytes of traces and spans ingested over your selected retention period.
You can view the data in three ways:
- Ingested size over time — Total data size ingested per month
- Count over time — Number of traces/spans ingested per month
- Avg size per trace/span — Average size of each trace or span
Online Evals Ran Per Month
This section shows your online evaluation usage over time. Online evals are evaluations run on your production traces and spans in real-time. You'll be charged based on the total number of metric evaluations run beyond your plan's included limits.
The chart displays the number of online evals executed per month, helping you track evaluation volume and identify usage trends.
Signals Ran Per Month
This section shows your classifier usage over time. Each classifier evaluation on a trace or idle thread is counted as one signal run. You'll be charged based on the total number of signals run beyond your plan's included allowance.
The chart displays the number of signals executed per month, scoped to whichever sample rates you've configured for trace and thread classifiers in Workflows → Classifiers.
Cost Insights
The Cost Insights tab shows what this project has spent in a billing cycle. Pick the cycle from the billing cycle picker at the top of the tab.
Spending Summary
Summary tiles show the project's Total spending for the cycle, its spend on Online evals, Offline evals, Signals, and Platform features, and % of org total, this project's share of your organization's spending.
Total Spending Over Time
A chart of the project's spending across the selected billing cycle.
Evaluation Cost
Evaluation cost for this project, broken down by where the evals ran. Select a tab (All, Trace, Span, Thread, or Test run) to see cost by each.
Signals Cost
Signals (classification) cost for this project, broken down by the traces and threads that were classified (Trace and Thread tabs) and by the classifier that ran (Classifier tab).
Usage Limits
The Usage Limits tab lets you cap this project's usage per billing cycle. Leave a limit blank (No limit) to keep going and pay for any overage.
| Limit | What happens when it's reached |
|---|---|
| Signals | New signals stop being generated until the next cycle |
| Trace Storage (GB-months) | New traces are rejected until the next cycle |
| Online Evals | New online evaluations stop running until the next cycle |
Last updated on