Usage, Billing, and Plan Limits
Telemetry exposes plan and usage information in team settings and when a free-plan limit affects querying. The product tracks storage and query-duration usage for plan enforcement.
Numeric allowances, prices, and commercial terms can change. Use the live pricing page and your team plan settings as the source for current limits rather than copying a number from an old screenshot, proposal, or runbook.
Review current usage
For the active team, inspect:
- current plan;
- stored data usage and the plan storage allowance;
- accumulated query-duration usage and its allowance;
- the billing or plan-management destination available to the team;
- any current upgrade or overage terms shown before confirmation.
Usage displays are operational estimates for managing the service. Do not use them as a replacement for your own customer billing ledger or audited financial records.
What happens at a free-plan limit
When the free plan exceeds an enforced storage or query-duration allowance, a query path can be blocked and the product can present an upgrade action with the current usage values. Ingestion, retention, and other behavior may have separate current rules; verify the live plan terms instead of inferring them from a query message.
If a production dashboard or alert is important, do not wait for a limit to interrupt it. Assign an owner to review usage and plan headroom on a regular schedule.
Reduce avoidable usage
Start with instrumentation and query design:
- Send one canonical outcome event per useful unit of work instead of duplicating raw logs.
- Exclude noisy fields and payload copies that will never be queried.
- Use bounded route templates and categories instead of raw URLs and messages.
- Apply appropriate table retention.
- Filter selective time ranges and partitions.
- Avoid repeatedly scanning a broad table when a narrower reviewed query answers the question.
- Export intentionally rather than using the interactive query path for large extracts.
Do not sample or delete security, billing, incident, or exact reconciliation events merely to reduce cost without an approved data policy. The Telemetry Cost Management guide explains how to measure volume without copying event payloads.
Plan a change
Before changing plans:
- identify the team and current plan;
- review recent storage and query-duration trends;
- inventory dashboards, alerts, reports, and exports that depend on continued access;
- confirm the displayed price, allowance, overage, and cancellation terms;
- record the billing owner and internal approval;
- verify the new plan in team settings after the change.
For an unexpected charge or a mismatch between the product and your commercial agreement, preserve the team identifier, billing period, relevant screenshots, and invoice reference, then contact Telemetry through the support channel shown in the product.
Continue with Data Retention and Deletion, Partition Columns, and Exporting Query Results.