There are several metrics missing on our Concourse CI:
concourse_tasks_waiting_durationconcourse_tasks_waiting
which really important for autoscalling and tracking user pipeline delays
concourse_tasks_watingin metrics appeared on prometheus service endpoint.
Actual results
Port forward:
kubectl port-forward service/concourse-web-prometheus -n concourse 9391:9391
Forwarding from 127.0.0.1:9391 -> 9391
Handling connection for 9391
Handling connection for 9391
In terminal:
$> curl http://localhost:9391/ | grep wait
# HELP go_memstats_heap_idle_bytes Number of heap bytes waiting to be used.
dmytro@centos: ~/Documents/refi/sdp-app-deploy $>
Other metrics are present.
Additional context
Concourse run in AWS EKS, deployed with Helm Chart.
Summary
There are several metrics missing on our Concourse CI:
concourse_tasks_waiting_duration
concourse_tasks_waiting
which really important for autoscalling and tracking user pipeline delaysSteps to reproduce
Deploy Concourse CI with Helm chart:
Expected results
concourse_tasks_watingin metrics appeared on prometheus service endpoint.
Actual results
Port forward:
In terminal:
Other metrics are present.
Additional context
Concourse run in AWS EKS, deployed with Helm Chart.
Triaging info