Hard to distinguish which metrics query is in play ... maybe this is a feature than a defect about kube-metrics-adapter

[mikkeloscar]

This is a problem I never considered, but I can totally see how it's not ideal to have the same query name used.

I would consider it a feature that we change/extend the metrics definition in a way where you can name the metrics in a custom way. In the past we were limited to the metricName as an identifier because we were using older autoscaling API versions, but now with autoscaling/v2beta2 being the default we can take advantage of labels on all the metrics.

I would propose we add something like type: prometheus-query as a label and then let users define a custom metric.name.

[prageethw]

Thanks @mikkeloscar

[prageethw]

@mikkeloscar any idea whether this feature will be done at all?

[mikkeloscar]

@prageethw I have it on my todo list, but didn't get around to implement it yet unfortunately. It's not forgotten but will take some time before I get around to it. Will also happily review PRs adding support :)