Runner cost vision
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Details
As part of Runner Fleet - closed as duplicate (&6720 - closed), I wanted to use this issue to provide the vision for solving the following problem:
Users who use cloud platforms (AWS, GCP, Azure, and more) to host their Fleet of runners do not have an easy way of knowing how much their runners are costing them or how much they are being used. The current flow they go through is finding the total compute cost in their cloud platform, and then trying to manually attribute that to jobs run in GitLab. They have no easy way to know who their top users are of their Instance runners (the ones any project can use) so they can “charge” those groups or projects accordingly or even update their Fleet to optimize pipeline performance for certain groups and projects. There's no way of knowing that certain runners are used most often. Finally, users don't have a way to optimize their costs based on previous data. For example, if they are spending $1K in 1 week, how do they lower costs while still maintaining pipeline performance? Another example is if one project attributes to the majority of the runner costs, how can the user optimize their Fleet (or even company organization) to account for the higher usage for that project?
Vision proposal
Added to dashboard
Full page report TBD