Quota Rules

Quota rules let you set enforced daily caps for how many units each entity type can ingest. Use them to keep usage within plan limits, prioritize what matters most, and reduce the risk of losing visibility when traffic spikes.

Quota rules let you set enforced daily caps for how many units each entity type can ingest. Use them to keep usage within plan limits, prioritize what matters most, and reduce the risk of losing visibility when traffic spikes.

When to use quota rules

Use quota rules to:

• Allocate capacity by priority so critical workloads keep ingesting when traffic spikes.
• Keep usage predictable with clear daily caps.
• Preserve visibility for essential data sources.
• Plan for growth by adjusting allocations as your usage changes.

Units and supported entity types

Coralogix uses a unit-based pricing model as a universal billing and capacity metric across observability entity types.

With quota rules, units are allocated per entity type. Entity types act as data types and objects across the Coralogix platform, breaking down data pillars into more granular units.

Currently, quota rules support these core entity types:

Entity type	Description	Pillar
logs	JSON event records	Logs
browserLogs	RUM browser events	Logs
spans	Trace span data	Spans
metrics	Metric time series and label sets	Metrics
sessionRecordings	RUM session recordings	Logs
cpuProfiles	Continuous CPU profiling data	Profiles
olly	AI agent interactions	AI

How quota rules work

When data reaches Coralogix, the ingestion layer evaluates it against your quota allocations. If an entity type reaches its allocation, Coralogix stops ingesting additional data for that category. Enforcement can take a few minutes to apply after the allocation is exceeded.

For data pipeline entity types (logs, spans, metrics, and similar), ingress blocking takes 1–5 minutes to take effect. For AI entity types such as olly, enforcement is applied at the AI service layer and the propagation window may differ. Blocked data or interactions are neither processed nor billed.

• Quota distribution: As you assign entity types, this pie chart shows how your daily quota is split between allocated and unallocated units. Each slice displays both the unit count and its percentage of your total daily quota.
• Last 7 days units: A stacked bar chart showing actual units ingested per day across all entity types, helping you visualize recent traffic patterns.
• Quota notification: A real-time banner that appears when an entity is blocked, providing immediate next steps (such as adjusting allocations, upgrading your plan, or contacting support).

What "blocked" means in quota rules versus TCO

• With quota rules, blocked entity types are not ingested, are not available for search or analytics, and do not incur cost.
• If data is ingested and later blocked through TCO, it can still incur a minimal ingestion cost.

Overflow behavior

Unallocated units form a shared pool.

• By default, only entity types with no explicit allocation can draw from the unallocated pool.
• If you enable Overflow for an allocated entity type, it uses its reserved allocation first, then can continue ingesting by drawing from the unallocated pool (if available).

Example: If you allocate 20% to logs and enable Overflow for logs, logs are guaranteed up to 20%, and can continue ingesting beyond that using unallocated capacity (if available).

Create quota rules

1. Navigate to Data Flow, then Quota Rules.
2. Choose an entity type and set the allocation as Percentages or Units. Use the Allocation slider or enter an exact value.
3. Use the Allocation control and the 7-day usage indicators to guide your decision.
4. Click Allocate in the Status column to activate the rule.
5. Click Save.

Quota rules let you cap total ingestion per entity type. Quota-based routing adds a second layer inside logs: it lets you downgrade or block specific subsets of logs as your daily quota is consumed, instead of relying only on fixed priorities or waiting until you hit a hard cap. This capability is configured as a policy type inside the TCO Optimizer (it is not a separate quota rule type).

When updating a quota rule, you'll see a preview of how the changes affect current allocations before saving. The side-by-side comparison of existing and updated quotas helps validate adjustments, prevent misconfigurations, and manage quotas with confidence.

Current and updated quotas are displayed in interactive pie charts, giving you instant clarity on allocation changes.

Create or edit a quota-based log policy

In the Quota Rules page, you can:

Preview quota-based behavior

• View all active quota allocations.
• Monitor usage with visual indicators showing the minimum, average, and maximum usage for each entity type over the past seven days.
• Review 7-day historical usage in a stacked bar chart that shows daily units ingested by entity type.
• Filter by pillar using the tabs to quickly scope the table to Logs, Metrics, Spans, Profiles, AI, and more.
• Select measurement type with the Percentages | Units switch to control how allocations are displayed and edited.
• Show only active allocations by enabling the filter to hide unallocated rows.
• Adjust allocations using the Allocation column's slider or numeric input.
• Enable or disable Overflow using the Overflow toggle per entity type.
• Activate or deactivate rules by clicking Allocate or Unallocate under Status.

Understand the Priority column in log policies

As you assign entity types, the pie chart shows how your daily quota is split between allocated and unallocated units.

How quota rules and quota-based routing work together

Use both when you need hard limits and finer-grained control: * Use quota rules to enforce daily caps per entity type (for example, to ensure logs cannot consume all daily units). * Use quota-based routing inside logs to downgrade or block lower-value log subsets earlier, helping preserve quota for critical log traffic and reducing the chance that all logs are blocked due to a spike.

Quota-based routing for logs

Quota rules cap total ingestion per entity type. Quota-based routing adds a second control layer within the TCO log pipeline: it lets you downgrade or block specific subsets of logs as your daily quota is consumed, instead of relying only on fixed priorities or waiting until you hit a hard cap.

You do not need to configure quota rules to use quota-based routing — they are independent features that can be used separately or together.

This capability is configured as a policy type inside the TCO Optimizer—it is not a separate quota rule type.

How quota-based routing works

In the TCO Optimizer, standard policies apply one fixed priority (High, Medium, Low, or Block) to all matching logs.

Quota-based policies apply different priorities at different points in the day based on quota consumption. Evaluation happens continuously during ingestion. Quota-based policies currently support a single usage threshold (two priorities). Additional thresholds for multi-step degradation may be added in a future release.

Create or edit a quota-based log policy

1. Navigate to Data Flow, then TCO Optimizer.
2. Select Logs.
3. Select Create policy (or open an existing policy to edit it).
4. In Details, set Policy name (required), Description (optional), and Policy order (First or Last).
5. In Filters, define what the policy matches:
   • Use Builder for common conditions such as application, subsystem, and severity.
   • Use Expression to define advanced logic, including DPXL-based filters.
6. In Policy type, select Quota-based.
7. In Priority, configure how priority changes as quota is consumed:
   • Relative sets the threshold as a percentage of the daily team quota.
   • Absolute sets the threshold as a units value.
   • Configure:
     • Prioritize X (relative or absolute) of daily quota as High (or Medium / Low)
     • All remaining quota is automatically set to Block (this default cannot be changed in this release).
8. (Optional) Set Archive retention (None, Default, Short, Intermediate, or Long).
9. Review the Preview panel for impact on recent data (see next section).
10. Turn on Enable policy to activate immediately, then select Create.

Preview quota-based behavior

Use Preview to validate expected impact before saving:

• Switch between Last 24 hours and Last 7 days.
• Review Data sent and the estimated % quota and Units (U) impact.
• Use Group by to break down results by application, subsystem, or severity, and identify which combinations are consuming quota.

Preview reflects how the policy would have applied to recent traffic — it is not a guaranteed projection of future behavior.

Understand the Priority column in log policies

For quota-based policies, the Priority column can show a transition, for example High → Block. The highlighted value represents the currently active priority at that moment in time.

How quota rules and quota-based routing work together

Use both when you need hard limits and finer-grained control:

• Use quota rules to enforce daily caps per entity type—for example, to ensure logs cannot consume all daily units.
• Use quota-based routing inside logs to downgrade or block lower-value log subsets earlier, helping preserve quota for critical log traffic and reducing the chance that all logs are blocked due to a spike.

If a quota rule blocks the entity type entirely (daily cap exhausted), no further log traffic is ingested regardless of quota-based routing policies.

Notifications

When an entity type is blocked due to reaching its allocation, the Quota Rules page shows a banner with next steps—such as adjusting allocations, upgrading your plan, or contacting support. The banner clears automatically once the condition is resolved.

Permissions

Depending on which actions you want to execute in quota rules, the following permissions are required.

Resource	Action	Description
team-quota-rules:Read	Read	View quota rules.
team-quota-rules:Manage	Manage	Manage quota rules.