blossom capacity:show
Show capacity allocations
Usage
blossom capacity:show [--location LOCATION] [--id ID]
Flags
| Flag | Description |
|---|---|
--location |
Location id (defaults to profile or Account default) |
--id |
Capacity id. Omit to show all allocations in the selected Location |
Examples:
blossom capacity:show
blossom capacity:show --id capacity-100
BLOSSOM_OUTPUT=json blossom capacity:show
Without an ID, shows all capacity allocations in the selected Location, separated into App, Data, Persistent, Builder and dedicated resources. Each row identifies its owner, active allocation and estimated Blossom charge.
With an ID, shows that allocation’s details. App Capacity includes:
- Workload allocation: CPU and memory requested by Services and Jobs, including temporary rollout demand.
- Platform reserve: memory held for runtime services and safe delivery.
- Available headroom: room remaining in the active allocation.
- Ready allocation: capacity recorded as ready for delivery.
- Retained excess: active units above recorded required units. Retirement waits for demand, deployment safety and the retention policy.
These are allocations, not measured CPU/RAM utilization or physical Server totals. Shared databases and caches use Data Capacity; their engine allocations are not counted again. Persistent pools and Builders have their own allocations. Load balancers do not expose an App-style CPU/memory allocation.
Use capacity:server:list to inspect backing Servers and their lifecycle states.
Only App Capacity has a policy editable through capacity:update.
Manage other allocations through their owning resources. Use metric:* for
workload utilization and spending:show for Account-wide billing.