Open jmmesquitacardoso opened 3 years ago
I think that label, app=concourse-worker
, may be coming from the HPA
I am also very interested in knowing how to work around this :)
So it turns out there's a way to work around this with metric relabelling:
metricRelabelings:
- action: replace
sourceLabels:
- worker
targetLabel: pod
This way, the pod
label gets replaced with the worker
one, which points to concourse-worker
pods.
Consequently, the concourse worker HPA is now able to fetch custom metrics, as they are now associated to the concourse-worker
pods and not the concourse-web
one anymore.
Hi! We're using the customMetric
concourse_workers_containers
as defined in the chart's example, and we're using prometheus adapter along with it. The issue is that that concourse is calling the custom metric with theapp
label asconcourse-worker
, while the metric in Prometheus is being saved while associated with theconcourse-web
app. For example:The query being done to the prometheus-adapter is something along these lines:
This yields no result as the metric is associated with the
concourse-web
app. Therefore, changing the query to something along these lines retrieves the correct result:Is there any way in the chart to associate the
concourse_workers_containers
metric with theconcourse-worker
app so it can be successfully fetched?Thanks!