You need to enable JavaScript to run this app.
Torch Object Storage

Torch Object Storage

Copy page
Download PDF
FAQ
How do I know if the inventory file has been generated?
Copy page
Download PDF
How do I know if the inventory file has been generated?
Once a bucket inventory rule has been created, TOS will generate inventory list files based on the configured parameters. To ensure you get your inventory files in a timely manner, confirm their generation status directly in the console or via event notifications. This topic describes two methods for confirming whether an inventory file has been generated.​
Inventory files​
TOS generates inventory files based on bucket inventory rules. The following example illustrates the directory structure of these files.​
tip​
For more information, see Inventory files.​
​
destinationPrefix/sourceBucketName/inventoryId/YYYY-MM-DDTHH-MMZ/files/UUID.csv.gz​
dest_bucket​
└──destinationPrefix/​
└──sourceBucketName/​
└──inventoryId/​
├──YYYY-MM-DDTHH-MMZ/​
├──files/​
├──7fd76a1c421391260a481a3405c6****_0.csv.gz​
├──7fd76a1c421391260a481a3405c6****_1.csv.gz​
├──8s5sda632dwa89s2das3dw9dsa2s****_0.csv.gz​
....​
├──manifest.json​
├──manifest.checksum​
​
Method 1: Monitor the generation status using event notifications​
When a new manifest.json file appears in the destinationPrefix/sourceBucketName/inventoryId directory of the bucket, it indicates that the scheduled inventory file has been successfully created. You can set up event notifications to monitor changes to the bucket's resources. For example, you will receive a notification when a new manifest.json file is added. This lets you know that the inventory file is ready. This method is ideal for scenarios in which there are numerous objects in the bucket and generating the inventory file is time-consuming. For how to configure event notifications, see Delivering event notifications to veFaaS or Delivering event notifications to Message Queue for Kafka.​
Below is an example of an event notification rule configuration:​
​
Parameter​
Description​
Event name​
Enter a name for the event notification rule. For example, inventory.​
Prefix​
Enter the prefix in this format: destinationPrefix/sourceBucketName/inventoryId/.​
For example, if the inventory report prefix is "tos_bucket_inventory", the bucket name is "example", the rule name is "aaa", then you should set the prefix to tos_bucket_inventory/example/aaa/.​
Suffix​
Enter "manifest.json".​
Events​
Select tos:ObjectCreated:Put.​
Data target​
Select Function service or Kafka.​
​
Method 2: Check the inventory files directly in the console​
Inventory files are stored in the bucket's destinationPrefix/sourceBucketName/inventoryId/YYYY-MM-DDTHH-MMZ directory. The appearance of a new manifest.json file there indicates that the inventory file has been successfully created. This method is suitable for scenarios in which there are few objects in the bucket and creating the inventory file is quick.​
For example, if the inventory report prefix is "tos_bucket_inventory", the bucket name is "example", the rule name is "aaa", and the scan time is "2025-08-21T16-20Z", you can find the manifest.json file in the tos_bucket_inventory/example/aaa/2025-08-21T16-20Z/ directory. This indicates that the inventory file has been successfully created.​
​
Last updated: 2026.06.22 15:21:16