Yeah, it looks like the other metrics in the dashboard do this correctly (see https://github.com/aws/karpenter-provider-aws/blob/main/website/content/en/preview/getting-started/getting-started-with-karpenter/karpenter-controllers.json#L292). Can you copy what's present in the other controller_runtime metrics in that file and just apply that to this metric. That should allow us to select the controller dynamically in the dashboard.

@yogeek Is this something that you want to be assigned to if you're going to open the PR?

@jonathan-innis I think there is a misunderstanding : I think the issue is not on the metrics (which are using the "controller" variable as they should, like in the one you pointed out like : METRIC{controller=\"$controller\"}) but in how this "controller" variable's values are retrieved : using label_values(controller_runtime_reconcile_errors_total, controller) implies that all the controllers that expose the controller_runtime_reconcile_errors_total metric (karpenter is not the only one, aws-load-balancer-controller is also exposing it for example, and maybe other controllers as it is a quite common metric for a controller) are retrieved and listed in the "controller" variable's values, hence appearing in the drop-down variable filter.
However, the only controllers needed for the karpenter dashboard are karpenter's ones so we have to find a way to select only karpenter's label_values, and using {job="karpenter"} is one way to do.

I prepared a PR here #6181