Skip to content
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

Closed
vivekjainx86 opened this issue Jun 16, 2022 · 6 comments
Closed

PredictKube scaler ignores metricName value #3180

vivekjainx86 opened this issue Jun 16, 2022 · 6 comments
Assignees
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity

Comments

@vivekjainx86
Copy link

vivekjainx86 commented Jun 16, 2022

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:

- authenticationRef:
      kind: ClusterTriggerAuthentication
      name: predictkube-auth-secret
    metadata:
      historyTimeWindow: 7d
      metricName: web_predicted_requests_per_second_per_pod
      predictHorizon: 2h
      prometheusAddress: http://<prometheus-url>:9090
      query: <prometheus-query>
      queryStep: 5m
      threshold: "15"
    metricType: AverageValue
    type: predictkube

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.

@vivekjainx86 vivekjainx86 added the bug Something isn't working label Jun 16, 2022
@tomkerkhove tomkerkhove moved this to Proposed in Roadmap - KEDA Core Jun 16, 2022
@tomkerkhove
Copy link
Member

@daniel-yavorovich can you help on this?

@vivekjainx86
Copy link
Author

hello @tomkerkhove, can I work on this? I already made code changes, and working on test cases.

@zroubalik
Copy link
Member

@vivekjainx86 sure, that's even better :) Thanks!

@zroubalik zroubalik moved this from Proposed to In Progress in Roadmap - KEDA Core Jun 16, 2022
@tomkerkhove
Copy link
Member

Thanks!

@stale
Copy link

stale bot commented Aug 15, 2022

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Aug 15, 2022
@stale
Copy link

stale bot commented Aug 31, 2022

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Aug 31, 2022
Repository owner moved this from In Progress to Ready To Ship in Roadmap - KEDA Core Aug 31, 2022
@JorTurFer JorTurFer moved this from Ready To Ship to Done in Roadmap - KEDA Core Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale All issues that are marked as stale due to inactivity
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants