-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PredictKube scaler ignores metricName value #3180
Comments
@daniel-yavorovich can you help on this? |
hello @tomkerkhove, can I work on this? I already made code changes, and working on test cases. |
@vivekjainx86 sure, that's even better :) Thanks! |
Thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed due to inactivity. |
Report
While using PredictKube scaler, I observed that it ignores given metricName value, and uses pre-defined prefix (here) . Because of this, the metric is not uniquely identified if I use multiple predictKube scalers.
Example:
Expected Behavior
It should set metric name as:
s0-predictkube-web_predicted_requests_per_second_per_pod
Actual Behavior
It sets metric name as:
s0-predictkube-predictkube_metric
Steps to Reproduce the Problem
To reproduce the issue, you can use predictkube scaler in scaledobject, and see externalMetricName in scaledobject's status.
KEDA Version
2.7.1
Kubernetes Version
1.21
Scaler Details
Predictkube
Anything else?
I will make change and raise the PR.
The text was updated successfully, but these errors were encountered: