Add job
label by default when using Prometheus collector
#13878
Merged
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.
This PR adds
job
label by default when using prometheus collector. So when using raw Prometheus collector it will always beprometheus
.When using lightweight modules it is the name of the lightweight module ie
cockroachdb
Closes #12739
Testing:
metrics_path: /metrics
in the configuration and collect metrics from anode-exporter
directly.metrics_path: '/federate'
and collect metrics from Prometheus server.In both cases label
job
should be present.https://www.elastic.co/guide/en/beats/metricbeat/master/metricbeat-metricset-prometheus-collector.html
Extra: Try the same with
cockroachdb
lightweight module. Unitest's testdata cover this case too.