Assigned
Status Update
Comments
li...@google.com <li...@google.com> #2
Summary from Eng Team:
The repository size metric does have a bug whereby if updates to the repository happen rapidly, the metric will show the incorrect size of the Repository. Specifically it will show a much higher size that is correct. We are aware of this issue and are looking at ways to fix it. We may require customers to migrate to a new version of this metric to get the correct repository size values.
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered:
Looking into Metric Explorer, we saw that the Artifact Registry size graph shows the incorrect size of the repository
What you expected to happen:
WE expect that Metric Explorer will show the accurate size of the Repository
Steps to reproduce:NA
Other information (workarounds you have tried, documentation consulted, etc):