Usage
What this screen is for
Usage on the platform plane shows the billable operations the licence server recorded for the whole installation, every tenant together, period by period over a range of UTC days you choose. Each row is one period with its state and its Total operations, Streaming operations and Non-streaming operations; read by month, a row also says on how many of its days usage was recorded. Every figure is the licence server's.
Nothing here changes anything, and this screen offers no export. The decisions are which grain to read, over which range, and how far to trust each figure given its period's state.
What must exist first
The screen is offered in system context only; opening it while a tenant is assumed takes you to that tenant's own Usage screen.
- The permission to read the platform licence shows the screen and its navigation entry. Every built-in platform role holds it: super administrator, operator, auditor and viewer. Without it the screen says Access restricted and names
platform.license.read. - The server also refuses a caller whose token is not the platform's, whatever permissions it carries.
- The licence server must answer. When it does not, the screen says The usage figures could not be read and offers Retry.
Decisions you make here
Knowing what is counted
The read covers the whole installation: the screen asks for no tenant, so every figure is the sum over every tenant of the installation. Only billable operations are counted; a request that was refused or that failed is never counted. Each column is named by the figure the licence server identifies for it, the same name the License screen gives it. Current as of states when the figures were last brought up to date.
Beneath Current as of, one sentence states how many final days of the range recorded no usage, for example Usage records on this installation start on 24 Sept 2026. Final days since then that recorded no usage: 2 of 2, through 25 Sept 2026. The licence server counts it over the whole range, whichever page is on screen, and counts only final days since this installation's usage records start: not a day before them, not today, and not a day whose figures may still grow.
When no day can be counted yet, the sentence says why instead, for example Usage records on this installation start on 26 Sept 2026; no day since then is final yet. When the range recorded no usage, the sentence is left out if every day could be counted; otherwise it states only what limits the count: when the usage records start, that the licence server could not confirm when they start, or that no day is final yet. Numbers and dates are written in the language the console is set to.
These are not the operation counts shown elsewhere in the console. Platform Overview counts audit records, and the key reports count each key's own counter, which a rotation resets.
Choosing the range and the grain
The screen opens on Last 30 days, by day. Last 7 days, Last 30 days, This month, Last month and Last 12 months read their range as soon as you press them; Last 12 months reads by month, the others by day. The line under the controls always states the range the figures belong to, for example Showing 26 Aug – 24 Sept 2026, by day (UTC).
For another range, change From and To and press Apply; nothing is read while you type. The ends are inclusive UTC days. Apply stays unavailable, and the screen says This range cannot be applied and why, until both ends are set, the start is not after the end, and the ends are at most 366 days apart by day or 24 months apart by month. Escape or Cancel puts back the range on screen. There is no all-time reading.
Day and Month apply at once. A range you applied yourself is kept when the new grain can answer it; otherwise the range becomes that grain's default, the last 30 days or the last 12 calendar months.
The applied range and grain are part of the page address, so a reload keeps the view and a shared link opens it. A link whose range could not be applied opens the default view instead, and says so.
Reading a range longer than one page
The server answers a page of periods at a time, 50 by default. When the range holds more periods than one page, a line states which periods are on screen out of how many the range holds, and Earlier periods and Later periods move through them. A table without that line holds the whole range.
Trusting a period's figures
Each period carries a state:
- Open — may still grow: the period has not ended, so its figures are not a total.
- Provisional — period ended, figures may still grow: the period ended but the licence server has not yet established that it ingested everything up to its end. This is the ordinary state of a period that just ended; it does not mean data is missing.
- Final: ingestion was observed past the period's end, and the figures will not change.
Days with usage, shown when you read by month, says on how many of the month's counted days usage was recorded, for example 3 of 27. Only days whose records this installation holds are counted, from the day it was installed up to today, so on the day of installation the month reads 1 of 1, not 1 of 27. A counted day with nothing recorded had no usage or, while the month is not Final, can still gain some; the sentence under Current as of is where the days that recorded no usage are counted.
When the licence server could not confirm when this installation's usage records start, no day of the month is counted and the cell reads Not counted. Read by day there is no such column: every row is a day that recorded usage. A state or a count the source did not send reads Not stated, never Final.
Reading the consumption bar
When the source publishes a limit for a period, a bar compares the most recent period in the range with that limit and states the figures, without capping them at 100%. It appears only when every period of the range is on screen; otherwise a note says the reading is withheld and asks you to narrow the range. What the limit means commercially is set by your agreement. In this release the source publishes no limit, so no bar is shown.
Telling no usage from no answer
No usage was recorded in this range means the licence server answered and recorded no billable operation in any period of the range. The usage figures could not be read means the figures were not obtained: the screen says The licence server did not return the figures for this range. This is not a report of zero usage. Retry, and if it persists, check the licence server.
How it relates to other screens
View detailed usage on the License screen opens this screen on the current month to date. The License screen's own operation-usage panel is a fixed summary of that month for the installation: the same three operation figures, the split between streaming and non-streaming, and the payload bytes. Its day-by-day detail is this screen.
A tenant administrator reads the same figures for one tenant, and can export them, on the tenant's own Usage screen:
The per-key reports count each key's own counter, not the recorded usage shown here: