<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=31039) </details> <!--IssueSummary end--> ### Problem to solve In the admin panel, I'd like to know which repository is taking up how much of my disk space. Currently I see that some repositories are taking up much, yet I know that some repositories have images towards hundreds of gigabytes. Would it be possible to count the size of these images towards the total size as well? ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> Sidney (Systems Administrator) ### Further details "My server is full, but all repos are barely a few mb big" would be a possible consequence of not counting the registry size. The registry can get quite big. ### Proposal  Add a field for registry size / image size in the admin panel single-repository view Additionally count it towards the total size of a repository in the admin panel #### Further details 1. Will we display storage usage for new image repositories/projects/groups/namespaces as soon as the feature is available? Will this be confusing for users if we are only displaying partial storage usage? Starting in phase 2, we'll present any information we have on the container registry list page, but we will not present any namespace level data until a given namespace has completed phase 2 of the migration and all of their storage is accounted for. João's comment summarizes this [here](https://gitlab.com/groups/gitlab-com/packaging-and-pricing/-/epics/50#note_718318167). 1. Once storage visibility for the container registry is available, will it be enforceable? Yes. @amandarueda confirmed this in our most recent consumption pricing sync. 1. We deduplicate storage costs, so if the same base layer is uploaded multiple times, we only count 1. How will we charge for this then? In other words, who pays for it? Good question. That’s the tricky part of the usage calculations, as we have to deduplicate costs, otherwise, we’re overcharging. In general, when showing an “image repository” usage we sum the size of all layers within. For the “project” usage we’ll have to sum the size of all unique layers across all image repositories. For the “group” usage we have to sum the size of all unique layers across all projects. Finally, for the “top-level namespace” usage we have to sum the size of all unique layers across all groups. So if two customers use the same layer we should charge them both IMO. Otherwise, we’re leaking information about customers to each other (and we would have a new layer of complexity to the usage calculations).