- Ya
- 9 Agosti 2026, 04:42 UTC
- Mwandishi
- kamo
- Ahadi ya
- 3fc9978
The tab said "No usage data available for this period" for every organization. billingApi.getCurrentUsage() is a stub returning { meters: [] }, and UsageMeters renders its empty state at zero meters — so the message was reporting the stub, not the data. StorageUsagePanel reads the real BillingService endpoint and shows the two figures that are easy to conflate side by side: what the organization is holding right now, which falls when files are deleted, and what it has added over its lifetime, which does not. Alongside them, what moved this period, and a per-domain breakdown across documents, mailboxes, knowledge-base media, meeting recordings and disclosures. Where a figure is a floor rather than a measurement, it says so — a removal total with no opening snapshot behind it, or a lifetime total for a storage area that hard-deletes its records. A chip explains the record basis: an org is counted for every file it holds even though Kamo stores one copy per hash. The trend renders only once two days of history exist; one point is not a trend, and drawing it would imply a history that has not been collected yet. Series colours are the validated categorical order — worst adjacent CVD ΔE 9.1, worst adjacent normal-vision ΔE 19.6 on this surface. Three sit below 3:1 contrast, so the breakdown table is not decorative: it is the non-colour reading of the same data. Byte counts stay strings end to end (BillingService serializes Long via ToStringSerializer) and are only widened where the magnitude is provably safe.