Configuration options
For your inventory reporting configuration, you can specify the following options:- Schedule: How often you want the inventory report to run, either daily or weekly.
- Source bucket: Choose the bucket that you want to inventory. You can choose to list all of the objects in the bucket or only objects with a specified prefix. If you don’t specify a prefix, the report inventories all objects.
- Destination bucket: Choose the bucket where you want to write the inventory reports, and optionally specify a prefix (subdirectory) to organize the reports.
- Output formats:
- JSON, CSV, or TSV files compressed with GZIP.
- Parquet files compressed with Snappy.
- Optimized row columnar (ORC) files compressed with ZLIB.
- Optional fields: Choose the optional fields that you want to include in the inventory report. See the detailed field reference for all available configuration options.
Output fields
When you configure your inventory report, you can choose whether to include or exclude certain fields from the output. The report always includes some fields, and includes optional fields only if you specify them in theOptionalFields configuration. The following fields are available:
Notes and limitations
Before you enable Inventory Reporting, review the following considerations:- No notifications: You don’t receive notifications when the inventory listing completes, so you must check the destination bucket to see whether the inventory reports have been written.
- Pricing: Inventory Reporting incurs charges for storage of the inventory reports in your destination bucket. Use
LastAccessedDateto derive the access tier (Hot, Warm, or Cold) of the objects. For a workflow that usesLastAccessedDateto safely reclaim capacity, see Delete cold objects. - Consistency: Inventory reports provide eventual consistency. A specific report might not reflect object changes during the scan, but changes converge across successive runs. Reports aren’t transactional snapshots.
- Not for billing: Inventory reports are for governance and analytics, not billing reconciliation. Inventory reports don’t match the audit logs or the billing data exactly.
- Configuration limit: You can set up to 1,000 inventory configurations per bucket.
- Encryption: SSE-C for report files is not supported.
Inventory report contents
After an inventory run completes, the destination bucket contains the following report artifacts:- A manifest file (
manifest.json) that describes the report and lists all inventory data files. - One or more inventory data files that contain the object listings.
Manifest file
The manifest file (manifest.json) describes the inventory report, and it’s written to the root of the subdirectory specified in the inventory configuration. The manifest file is a JSON object with the following fields:
The manifest file looks similar to this:
manifest.json
Support
If you need help with Inventory Reporting, contact CoreWeave support or emailsupport@coreweave.com.