Add a base_job_name tag to encompass all instances of a given job #482
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When outputting Prometheus metrics, k6-operator includes a
job_name
tag, but the value of this tag corresponds to the individual instance (== Pod) running a test. So, for a job calledtest
, the values ofjob_name
look liketest-1
,test-2
, etc.This makes it very difficult to build a dashboard that displays all jobs running a particular test. We need a tag that provides the name of the job without any instance numbers.
This PR adds a
base_job_name
tag that contains only the job name.In the example above, this PR adds a
base_job_name
tag with a value oftest
.