-
Notifications
You must be signed in to change notification settings - Fork 1.5k
expand gitlab_runner supported metrics #21261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
expand gitlab_runner supported metrics #21261
Conversation
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files🚀 New features to boost your workflow:
|
01ff9a3
to
8cc71d8
Compare
gitlab_runner.autoscaling_machine_states,gauge,,,,The current number of machines per state in this provider.,0,gitlab_runner,autoscaling machine states, | ||
gitlab_runner.autoscaling_machine_stopping_duration_seconds_bucket,gauge,,request,second,Histogram of machine stopping time.,0,gitlab_runner,autoscaling machine stopping duration time, | ||
gitlab_runner.autoscaling_machine_stopping_duration_seconds_count,gauge,,request,second,Histogram of machine stopping time.,0,gitlab_runner,autoscaling machine stopping duration time count, | ||
gitlab_runner.autoscaling_machine_stopping_duration_seconds_sum,gauge,,request,second,Histogram of machine stopping time.,0,gitlab_runner,autoscaling machine stopping duration time sum, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update! Adding the metrics to metadata.csv
does not ensures the metrics are going to be emitted. These metrics need to be allowlisted (see here). You need to add the metrics that you want to be allowed in the configuration spec.
Once you add them CI will fail telling you to update the config example. Should guide you to get it fixed.
Could you also include a changelog for this? Let me know if you need help with any of these steps.
Adding new metrics in a OpenMetricsCheck
is safe since we will only emit the metrics if they are found in the Prometheus endpoint. So there is no need to split per version.
Sadly, the suggested
|
What does this PR do?
This PR expands the list of supported metrics to include the ones that ship with Gitlab Runner 18.0+ as well as the new recommended docker_autoscale runner
Motivation
Would rather not pay custom metrics for those
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged