When the catalyst-api was run inside catalyst, we used VM Agent to collect the metrics and then added the catalyst=true label in the VM Agent config.
Now, for the standalone Catalyst API we use Kubernetes prometheus scrape which does not add this label. At the same time, we use this label in a really high number of charts, so the simple fix is to just add this label here.
An alternative would be to update all Grafana charts that use catalyst=true metric with a condition app_kubernetes_io_name="catalyst-api". However I see there are really a lot of these charts, so I'm not sure there is a simple way to update them all.
When the catalyst-api was run inside catalyst, we used VM Agent to collect the metrics and then added the
catalyst=true
label in the VM Agent config.Now, for the standalone Catalyst API we use Kubernetes prometheus scrape which does not add this label. At the same time, we use this label in a really high number of charts, so the simple fix is to just add this label here.
An alternative would be to update all Grafana charts that use
catalyst=true
metric with a conditionapp_kubernetes_io_name="catalyst-api"
. However I see there are really a lot of these charts, so I'm not sure there is a simple way to update them all.