Troubleshooting Storage Insights issues

This document provides solutions to common issues you might encounter whenusing Storage Insightsinventory reports ordatasets.

Common issues

This section provides guidance on how to resolve commonly-encountered issuesusing inventory reports and datasets.

Multiple inventory reports being generated daily

Issue: My inventory report configuration is generating multiple inventoryreports on a daily basis.

Solution: If you have more than 1,000,000 objects in your bucket, multipleinventory reports can be generated asshards. An inventory reportconfiguration generates one inventory report for every 1,000,000 objects in thebucket. For example, if you have a bucket with 3,500,000 objects, the inventoryreport configuration on the bucket will generate four inventory report shardsper the frequency you specify, along with amanifest file that containsthe number of generated inventory report shards and their file names.

Inventory reports not appearing in the destination bucket

Issue: My inventory reports aren't appearing in the destination bucket.

Solution: If you've created an inventory report configuration and don't seeinventory reports being generated in the destination bucket, check thefollowing:

  • Make sure the start date specified in the inventory report configurationmatches your expectation for when inventory reports should be generated. Forinstructions on how to specify a start date, seeCreate an inventory report configuration.

  • View your inventory report history to check for failures and their rootcauses. To see your inventory report history, complete the following steps:

    1. In the Google Cloud console, go to the Cloud StorageBuckets page.

      Go to Buckets

    2. In the list of buckets, click the name of the source bucket that containsthe inventory report configuration.

    3. On theBucket details page, click theInventory reports tab.

    4. In the list of inventory report configurations, click the UUID of theinventory report configuration that generated the reports you want tocheck.

    5. Check for failures in theInventory report history section. You canhold the pointer overHelp ()to get details about why a failure occurred.

  • Make sure the project-level service agent is granted the IAMroles required for reading and writing inventory reports. For instructions,seeGrant required roles to the service agent.

Inventory report delays

Issue: I'm seeing random delays with the generation of inventory reports.

Solution: The interval of time between inventory reports being generatedcan vary. You might see a delay of up to one day.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-17 UTC.