Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,331
    • Merge requests 1,331
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #350905
You need to sign in or sign up before continuing.
Closed (promoted) (promoted)
Open
Issue created Jan 21, 2022 by Tim Rizzi@trizziDeveloper

Data transfer visibility for the container registry

Context

GitLab.com has data transfer limits for data that moves outside of GitLab infrastructure. For example, a container image that is downloaded to a production environment. Depending on the frequency in which images or tags are downloaded from the Container Registry, data transfer costs can exceed the GitLab limit.

Self-managed customers are also interested in understanding the amount of data being transferred outside of their network as any inefficient use of their network will waste money.

Problem to solve

The problem is that GitLab doesn't surface this data for customers. So, as an Admin, you have no visibility into how much data is being transferred using the GitLab Container Registry.

Proposal

GitLab will create a dashboard or add to the existing usage quotas dashboard to ensure that data transfer for the container registry is measured and displayed for Admin. This will allow you to identify and remediate any inefficient usage of the container registry.

Assignee
Assign to
Time tracking