Geo : Ping usage for accelerated runner jobs by secondary sites
Problem to solve
We have some customers using Geo secondary sites to accelerate runners. Currently we don't have usage ping metrics for this use case.
Intended users
User experience goal
Enable product managers and data analysts are GitLab to easily retrieve this metric data from Sisense.
Proposal
We want to collect metrics for the number of runner jobs completed cloning from secondary Geo sites. We already have a metric for unique monthly secondary users that use the web UI at secondary Geo sites and we are planning to add a metric that tracks
Further details
Accelerating runners using Geo secondary sites is becoming popular amongst our customers. We currently don't have any metric data to support our decisions around this use cases. There are enhancements on our roadmap that can enhance benefit this use case.
Permissions and Security
TBD
Availability & Testing
This feature should be available when or short after we GA runner acceleration via Geo secondary sites.
Testing should ensure counting captures all use cases where runners are accelerated by secondary sites.
Available Tier
Not a customer facing feature
Feature Usage Metrics
N/A
What does success look like, and how can we measure that?
Is this a cross-stage feature?
No
What is the competitive advantage or differentiation for this feature?
We see usage ping data related CI jobs accelerated by secondary Geo sites from customers that have enabled usage ping and are using Geo to accelerate runners.
Links / references
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.