Quota Rules

Quota Rules in Coralogix allow you to define hard limits on the volume of data ingested by entity type—such as logs, metrics, or spans—to maintain control over resource usage, prevent unexpected costs, and ensure operational stability.

Use Quota Rules to:

• Optimize resource allocation. Manage diverse data types under a single account while maintaining fine-grained allocation and control aligned with team or product priorities.
• Maintain control through predictable usage. Align data usage with business goals through predefined, enforceable policies.
• Protect access to critical data. Ensure critical operations are safeguarded by reserving quota for essential workloads, reducing the risk of resource exhaustion.
• Support scalability. Implement a structured quota system that grows with your organization.

Supported entity types

Coralogix uses a unit-based pricing model across most observability features. A unit serves as a universal billing metric for all data types.

With Quota Rules, units may be 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 six core entity types, with more to be added. Each entity type is associated with a distinct data schema.

Entity type	Description
logs	Freeform JSON event
browserLogs	RUM browser event
spans	Spans
metrics	Metric series and labels
sessionRecordings	RUM session recordings
cpuProfiles	Continuous CPU profiling data

How it works

When data is sent to Coralogix, it’s inspected at the ingestion layer. You can allocate some or all of your units to specific entity types. This approach focuses on data type prioritization, rather than team-based allocation.

Once an entity type reaches its allocated quota, Coralogix automatically blocks ingestion for that type. The Ingress blocking, which can take 1 - 5 minutes to take effect, ensures no additional data is ingested and no overages are incurred. Blocked data is neither ingested nor billed.

Quotas reset automatically at 12:00 UTC at the start of each new quota cycle.

Overflow behavior

By default, any unallocated units are pooled and available on a first-come, first-served basis to unallocated entity types. However, you can activate the Overflow feature to allow allocated entity types to also use this shared pool.

Example

If you allocate 20% of your units to logs, activating Overflow for logs ensures:

• Logs are guaranteed at least 20% of your units.
• If additional unallocated units exist, logs may continue ingesting beyond the 20% minimum.

You can toggle the Overflow option per entity type to enable or disable this behavior as needed.

Create quota rules

To create a new quota rule:

1. Go to Data Flow > Quota Rules.
2. Choose an entity type and set the percentage of your total units to allocate. The UI displays average usage over the past 7 days to help guide your decision.
3. Toggle the Status switch to activate the rule.
4. Click Save.

Modify existing quota rules

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 teams validate adjustments, prevent misconfigurations, and manage quotas with confidence.

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

View and manage quota rules

In the Quota Rules UI, you can:

• View all active quota allocations.

• Monitor usage with visual indicators showing minimum, average, and maximum usage over the past 7 days.

• Receive notifications if an allocation is exceeded.

• Activate or deactivate rules using the Status toggle.

Permissions

Depending on which actions you would like to execute in Quota Rules, the following permissions are necessary.

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