Resource Usage | Zyeon UI

Preview in your theme

status="ready" · 12 heterogeneous resources in 4 groups: percent / cores / duration / bytes / bytes-per-second / count / money each take their own formatter (63% · 1.85 / 4 vCPU · 2h 29m / 10h · 1.64 / 2.00 GiB · 90.0 MiB/s · 8,420,311 / 10,000,000 requests · $318.40 / $500.00). Clicking a group header really collapses it — the rows unmount, leaving no invisible Tab stops, while the header keeps its alert chip so collapsing never folds an alert away. "Sort by usage" in the corner reorders by fill ratio descending: rows move within their group and groups follow their fullest row, with quota-less rows always last. Log retention is over quota: the track rescales to the actual usage, the quota position keeps a tick plus a hatched overflow segment rather than drawing past the end, and the chip reads "+10.0 GiB". Peak throughput has no quota, so that row draws no bar at all.

Cluster resources12 resources

CPU utilizationprod-cluster-1 · 8 vCPU63%
vCPU allocationburstable pool1.85 / 4 vCPU46%
Build minutesresets on the 1st2h 29m / 10h25%

Block storagepd-ssd · europe-west4Near limit1.64 / 2.00 GiB82%
Postgres storageprimary + WALCritical19.5 / 20.0 GiB97.5%
Log retention30-day hot retentionOver quota by 10.0 GiB110 / 100 GiB110%
Snapshotsdaily, 7 kept4.00 MiB / 2.00 TiB<0.1%

Egressbilling period to date743 GiB / 1.00 TiB73%
Peak throughput5-minute peak90.0 MiB/s
No quota — usage only
API requestsNear limit8,420,311 / 10,000,000 requests84%

status="ready" · the ungrouped billing-panel shape: no group means no collapsible sections, and sortable={false} drops the sort button entirely (order is always the order passed in). Data transfer is 989 GiB against a 1 TiB quota — when the usage is under one whole unit of the quota, each side keeps its own unit and reads "989 GiB / 1.00 TiB" instead of collapsing to "0.97 / 1.00 TiB" and losing the magnitude; 96.6% clears 0.95 so it is critical, while Storage and Build minutes clear 0.8 and read near limit.

Billing period · usage5 resources

Seats18 / 25 seats72%
StorageNear limit412 / 500 GiB82%
Data transferCritical989 GiB / 1.00 TiB96.6%
Build minutesNear limit9h 12m / 10h92%
Usage charges$318.40 / $500.0064%

status="ready" · the binary ladder, side by side: each row title is the raw byte count and the right-hand side is what the component actually renders — 1,023 B / 1.00 KiB / 1,023 KiB / 1.00 MiB / 1.00 GiB. 1023 B is never rounded up to "1 KiB", and 1048575 B never becomes "1024 KiB", a rung that does not exist on the ladder. The first five rows have no quota, so no bar is drawn; the last puts 1023 B against a 4096 B quota and still reads "1,023 B / 4.00 KiB".

Binary ladder · formatter proof6 resources

1023 B1,023 B
No quota — usage only
1024 B1.00 KiB
No quota — usage only
1048575 B1,023 KiB
No quota — usage only
1048576 B1.00 MiB
No quota — usage only
1073741824 B1.00 GiB
No quota — usage only
1023 B against a 4096 B quota1,023 B / 4.00 KiB25%

status="loading" · skeletonRows={4}; the skeleton reuses the two-line geometry of a real row (title bar + readout bar + track), and the animation stops under prefers-reduced-motion

Cluster resources

status="empty" · the built-in empty copy (replaceable wholesale via emptyState)

Cluster resources

Nothing metered yet

Usage shows up here once this workspace has resources attached to it.

status="error" · Try again only renders when onRetry is passed, and clicking it really runs error → loading → ready — not decoration

Workspace usage

Couldn't read usage

The metering service didn't respond.

Current status: error

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro