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

Support "Value" metric type for RabbitMQ scaler #1314

Closed
1 task
knepe opened this issue Nov 4, 2020 · 9 comments
Closed
1 task

Support "Value" metric type for RabbitMQ scaler #1314

knepe opened this issue Nov 4, 2020 · 9 comments
Labels
feature All issues for new features that have been committed to feature-request All issues for new features that have not been committed to help wanted Looking for support from community needs-discussion

Comments

@knepe
Copy link

knepe commented Nov 4, 2020

Would like to be able to use "Value" metric type for the RabbitMQ scaler, instead of "AverageValue" as it is now.

Use-Case

Want to have min replicas set to 0, so it will have 0 replicas when queue is empty, but as soon as the queue for ex contains 1 to 300 messages it should scale to 1 replica, and between 300-600 it should scale to 2 replicas and so on. There is another issue requesting this feature here: #692

I built a local image to test it out and it works as expected if we use v2beta2.ValueMetricType instead of AverageValueMetricType, but it should be configurable and default to AverageValueMetricType I guess.

Specification

  • Make MetricTarget Type configurable
@knepe knepe added feature-request All issues for new features that have not been committed to needs-discussion labels Nov 4, 2020
@knepe
Copy link
Author

knepe commented Nov 4, 2020

Please discuss this if/how you want to solve this in a more generic way :)
I have a working image I'm using in my cluster here: main...knepe:main (should not be treated as a PR, but more like a POC)

@knepe
Copy link
Author

knepe commented Nov 9, 2020

Hey guys, have you had time to discuss this? @zroubalik

@jeffhollan
Copy link
Member

Discussed in our standup today - this seems like a good feature worth looking into. Adding to roadmap

@zroubalik
Copy link
Member

My only small remark is, how do we handle multiple scalers per ScaledObject? Do we want to allow mixed scenario, I am curious what is the behavior then, whether it won't be confusing for users.

Maybe not 🐱

@knepe
Copy link
Author

knepe commented Jan 15, 2021

Hey, any updates on this? :)

@avivgold098
Copy link

Hey, this very useful also for the Prometheus Scaler as well

@tomkerkhove
Copy link
Member

Can you create a dedicated issue for Promehtues please?

@zroubalik
Copy link
Member

I'd prefer some umbrella issue where we can track this effort, because imho it should be done for all scalers.

@stale
Copy link

stale bot commented Nov 27, 2021

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 Nov 27, 2021
@tomkerkhove tomkerkhove added the feature All issues for new features that have been committed to label Nov 29, 2021
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Nov 29, 2021
@tomkerkhove tomkerkhove moved this to Backlog in Roadmap - KEDA Core Feb 10, 2022
Repository owner moved this from To Do to Ready To Ship in Roadmap - KEDA Core Mar 30, 2022
@tomkerkhove tomkerkhove moved this from Ready To Ship to Done in Roadmap - KEDA Core Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature All issues for new features that have been committed to feature-request All issues for new features that have not been committed to help wanted Looking for support from community needs-discussion
Projects
Archived in project
Development

No branches or pull requests

6 participants