Enhance usage ping data to show proxied traffic statistic from secondary site(s) to primary site
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Now that Geo proxying is available to most customers and in the %15.1 we enable Geo proxying by default for all customers using separate URLs for secondary sites which is the majority of our cusomter base, it is useful to better characterise the data that is being proxied from the secondary site(s) to the primary site.
Today we only accelerate a subset of the data types that are replicated to the secondary Geo sites by serving read requests directly from the secondary site. By better understanding proxied data we can make better informed decisions on which additional data type could and should be accelerated in the the future. This data will allow us to evaluate and prioritise data types accordingly.
Problem to solve
Gain a better understanding of the data that is proxied to the primary site by the secondary site(s). We want to know the following for each data type replicated in the space of a week (7 days):
- How frequently a read request is proxied
- Total volume of data proxied
The data is to be aggregate on site and shared with GitLab via usage ping.
All policies, rules and due diligence related to usage ping should apply to this data. The opt-in from the customer should cover collection and transmission of this data.
Any documents or notifications related to usage ping to be updated to reflect collection of this data.
Proposal
Collect this aggregate information for each data type over the course of a week for each replicated data type. The information to collect for each data type:
- How frequently a request was proxied to the primary site..
- Total volume of data proxied.
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.