Quay.io Metrics for Monitoring Product Performance & Growth

Goal:

In order to best serve our internal and external stakeholders we must begin monitoring the health of the Quay product through tracking our metrics.

From this data we can derive meaningful information to influence business decisions that will affect the future investment, direction and development of the downstream Quay product.

Data needed:

• Median user profile (PROJQUAY-3058 and PROJQUAY-2281) of paid and unpaid users
• Public vs. private repo count (globally and median per user)
• Number of active users in the last per month
• Active in the UI (login / browse)
  • Active in their own user organizations (push and pull content)
  • Active in shared organizations (push and pull content)
  • Robot account usage vs. (generated) docker password usage from user accounts

• Percentage of user accounts and organizations with robot accounts vs. without with…
  • At least 1 robot account
  • 1-5 robot accounts
  • 5+ robot accounts

• Median amount of tags and pulls in public vs. private repositories
• Median storage consumption of public vs. private repos
• Total storage consumption
• Median storage consumption of content that was recently pulled (per month for the last 12 months)
• Median number of image pulls per paying vs non-paying accounts
• Median number of owned organizations per user
• Median number of organization a user is a member of
• Median amount of egress traffic per private and public organizations