Token Usage vs. Previous Period¶
On the Monitoring page, the token-usage comparison adapts to the date range you select. Instead of comparing against a fixed threshold, Trust3 compares the range you are viewing against the period immediately before it, so the trend always reflects your current view.
How the comparison works¶
- Select a date range on the Monitoring page.
- Trust3 compares two windows of equal length:
- Current period — the date range you selected.
- Previous period — the window of the same length immediately before it.
-
The difference is shown as a percentage change, with ▲ for an increase and ▼ for a decrease:
percent change = ((current − previous) / previous) × 100 -
Change the date picker and every value recomputes together — no manual baseline configuration is needed.
Where you see it¶
- Tokens column — each row shows the current total with a trend indicator, and the previous-period value beneath it. For example,
34.6K ▲ 209%with11.2Kshown below. - Asset slideout → Token Usage — shows the selected-range total, the percent change versus the previous period, and the baseline (previous-period) value. For example:
- Last 24h: 34.6K
- Up 209% vs the previous period
- Baseline: 11.2K
Worked examples¶
| Previous period | Current period | Displayed |
|---|---|---|
| 11.2K | 34.6K | ▲ 209% |
| 21.7K | 12.8K | ▼ 41% |
| 0 | 5K | ▲ 100% |
| 0 | 0 | 0% |
Percentages are always bounded: when both periods are zero the change is 0%, and when the previous period is zero and the current period is above zero the change is shown as +100%.
Anomaly count¶
The token anomaly count compares the total usage in your selected range against your cost policy limit, not against the previous period. For example, a 6-day view totaling 99K stays within a 100K cost-policy limit, even though a wider 7-day view might exceed it. Cost-policy alerts continue to work independently of this trend comparison.
Related documentation¶
- Policies — how cost and usage limits are defined.