You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oftentimes there may be sporadic changes in batch for GC buckets. When this happens, it might be nice to have an automated report which is manually or perhaps automatically generated and shared with stakeholders to help validate the number and size of objects stored before and after a large upload. This issue focuses on providing these capabilities, with the minimum being documentation for how to generate this information manually.
The text was updated successfully, but these errors were encountered:
Adding more here: perhaps an email with a listing of an object tree and object counts under the "dirs" could help provide lightweight visibility on this front.
Oftentimes there may be sporadic changes in batch for GC buckets. When this happens, it might be nice to have an automated report which is manually or perhaps automatically generated and shared with stakeholders to help validate the number and size of objects stored before and after a large upload. This issue focuses on providing these capabilities, with the minimum being documentation for how to generate this information manually.
The text was updated successfully, but these errors were encountered: