See who is blocked, why, and when it ends
When data stops arriving, the first questions are which team is affected, which limit stopped it, and when it starts again. The Overview tab of Usage & Quota answers all three on one page: the status of every team against its CX units and AI units plans, each block this cycle with its cause and the fix, and a forecast of whether the current rate lasts until the quota resets.
The Overview always reads the current cycle: today on a daily CX units plan, or the current calendar month on a monthly plan. To look at a past range, use the CX units or AI units tab instead.
What you need
- Access to Usage & Quota. See What you need on the Usage and quota page.
- To switch between the organization and any of its teams, you must be an organization admin of an organization with more than one team. Everyone else sees their own team.
- To move CX units from the Overview, you need organization quota manage access. See Move units between teams.
- To see Units moved this cycle, you need read access to the
dataplan.quota_eventssystem dataset.
Open the Overview
In Coralogix, navigate to Settings, then Usage & Quota. The page opens on the Overview tab, unless you last left it on the CX units or AI units tab. A link with ?tab=overview always opens the Overview.
- Organization level: As an organization admin, select Organization in the toolbar to see every team at once.
- Team level: Select Team, then select a team from the list. A team member who isn't an organization admin sees their own team, with no switch.
You can also open one team's Overview from the drill-down drawer. In the All teams table on the CX units or AI units tab, select a team row, then select the Overview tab in the drawer. See Drill into a team.
Use the menu at the end of the tab row to expand or collapse every section at once, or to copy a link to the page. Last updated shows when the figures were fetched. Select Refresh to fetch them again.
Read team status
Each team gets a status per plan:
| Status | What it means |
|---|---|
| Blocked | The team can't send data. A limit stopped it, and the tooltip says which one and when ingestion resumes. |
| Warning | The team is still sending, but is forecast to run out before the quota resets, or has passed its warning line. |
| Normal | The team is forecast to last the day or the cycle within its quota. |
When Pay-As-You-Go is on for a team, passing the daily quota or daily burst doesn't block it. The extra units are billed and data keeps flowing until 00:00 UTC. Pay-As-You-Go doesn't extend a monthly quota.
At organization level
The Overview shows one section per plan, then Blocks this cycle, All teams, and Units moved this cycle.
- CX units and AI units: How many teams are Blocked, in Warning, and Normal on that plan. On CX units, Quota rules blocked counts the entity types a quota rule stopped, and in how many teams. The rest of each of those teams keeps sending data. The chart shows the units each team used per day this cycle. The 8 teams that used the most are shown by name, and the rest are added together as Other.
- All teams: Each team's Write access, PAYG state, CX units left, CX status, AI units left, and number of Blocks this cycle. The table lists blocked teams first, then the teams soonest to run out. From a team's More options menu, select Why blocked, Show in Team mode, Open team details, or Move CX units to this team. To rebalance several teams at once, select at least two teams and select Move CX units.
At team level
The Overview shows one section per plan, then Allocations, Blocks this cycle, and Units moved this cycle.
On the CX units section, the cards depend on the plan's cycle:
- Monthly plan: Monthly quota left, Today's quota left against the daily burst, Forecast, and Safe daily spend.
- Daily plan: Today's quota left against the daily quota, and Forecast for the end of the day.
On the AI units section, the cards are Monthly quota left and Rate, which compares the AI units used so far with the share of the month gone. AI units have no forecast.
Read the forecast
Forecast projects the share of the quota used at the end of the cycle, or at the end of the day on a daily plan. When the quota is forecast to run out, the card says on which day and at about what hour, in UTC.
Safe daily spend is the most the team can use each day and still last the cycle. The card compares it with the team's current rate and says how far over or under the safe rate the team is.
On a monthly plan, select what the forecast is based on under Forecast basis: This cycle averages the CX units used so far this cycle, and 7 days averages the last 7 days. Use 7 days when usage changed recently and the cycle average hides it.
The charts below the cards show the same reading over time. Switch Chart reading between Burn-down, units left, and Burn-up, units used. Last 3 cycles compares this cycle with the two before it, as a share of each cycle's quota. On a daily plan, Last 7 days does the same for each day.
Check allocations and the unallocated pool
Quota rules reserve part of a team's CX units for one entity type. Every data type without its own rule shares the rest, the unallocated units. On the team level, Allocations shows how the team's CX units split between its quota rules and the unallocated units.
The Quota rules and unallocated units table lists each allocation with its Status, Reserved per day, units Left today, units Used this cycle, whether Overflow is on, and its Blocked days. A blocked allocation stops only its own entity type. When the unallocated units run out, every data type without a rule stops, and data types with a rule keep writing.
To change an allocation for your own team, select Adjust allocations. Quota Rules opens in a new tab.
Find out why a team was blocked
Blocks this cycle lists every block and warning this cycle, newest first. At organization level, a calendar marks each day red for a block or yellow for a warning, and the cards count Days with a block and Days with a warning. At team level, the cards count Blocked days, Blocks, and Units not taken (est.), the units estimated to have been dropped while the team was blocked.
For each block, the table shows its Type, Plan, when it Started, when it Lifts, the units Not taken, and Why: the cause and the fix. Search the table to find a block.
| Type | What stopped |
|---|---|
| Daily quota reached | All of the team's data, until 00:00 UTC. The team passed its daily quota and its 10% grace. |
| Daily burst reached | All of the team's data, until 00:00 UTC. The team passed the daily burst of its monthly plan. |
| Monthly quota reached | All of the team's data, until the next cycle. The team used its whole monthly quota. |
| Quota rule limit reached | Only the entity type the quota rule covers. Other data keeps flowing. |
| Unallocated units used up | Every data type without its own quota rule. Data types with a rule keep writing. |
| Warning | Nothing. The team crossed a warning line. |
A block that is still in effect reads Ongoing in the Lifts column, with the time it lifts.
Each row offers the action that fixes it, such as Move CX units, Enable Pay-As-You-Go, or Adjust allocations. Pay-As-You-Go covers the daily quota and the daily burst, not a monthly quota: for a monthly block, move CX units to the team.
Track units moved
Units moved this cycle lists every move of CX units between teams this cycle, newest first, with when it happened, the direction, the units, the teams on each side, and who moved them: You, an API key, or Coralogix. At team level, the list shows only moves to and from that team.
To move units, select Move CX units. See Move units between teams.