ChatDiagram
Try for free
technology · operations

Cedar Cloud Storage Usage

Cedar Cloud’s storage chart divides capacity by account and then by service. The inner ring answers who owns the storage, while the outer ring shows whether backups, media, logs or warehouse data drive the total. This hierarchy is useful in a cost review because it points teams toward the areas worth investigating before applying retention or lifecycle policies. The figures are in terabytes and should come from a dated inventory snapshot in a working report. Do not use the chart alone to decide what can be deleted: backups and logs may have recovery or compliance requirements. Pair it with retention rules and cost information. If there are dozens of buckets or folders, aggregate them before making a sunburst so the visual remains readable.

Type echarts-sunburstEngine echarts-sunburstUpdated 9/24/2026
Cedar Cloud — Storage Usage
Drawing preview
The request

“Create a sunburst chart for Cedar Cloud storage use in terabytes: Production 84 TB with Backups 44, Media 25 and Logs 15; Analytics 51 TB with Warehouse 31, Exports 12 and Scratch 8; Development 25 TB with Test data 15 and Builds 10.”

Then tryAdd an archive tier under Production.Change logs storage to 20 TB.
What is in this drawing

Read the decisions behind it.

01Identify ownership

use account names as the inner categories.

02Target the largest child

backups are the first storage-reduction candidate.

03Refresh snapshots

storage totals change, so date the source data.

Use for a limited set of cloud accounts and storage services with a common unit.

More like this

Other examples in this family.

Loading drawing…
Cold Storage Warehouse Zonesevent planningOpen →
Drawing preview
Clinic Delay Pareto CharthealthcareOpen →
Drawing preview
Delivery Delay HistogramlogisticsOpen →

Browse all sunburst chart templates →

FAQ

Common questions

Why group by account first?

It assigns ownership before showing the technical service using the capacity.

Can values be costs instead of terabytes?

Yes, provided every node uses the same cost period and currency.

Should temporary data be separate?

Yes, when it has a different retention policy or cleanup owner.