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

Add new "messageReceiveRateTarget" metric to Solace Scaler #4665

Closed
dennis-brinley opened this issue Jun 8, 2023 · 0 comments · Fixed by #4667
Closed

Add new "messageReceiveRateTarget" metric to Solace Scaler #4665

dennis-brinley opened this issue Jun 8, 2023 · 0 comments · Fixed by #4667
Assignees
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

Comments

@dennis-brinley
Copy link
Contributor

Proposal

Add a new messageReceiveRateTarget metric to Solace Scaler. This metric will allow KEDA to scale workloads based on the rate of message delivery to Solace PubSub+ queues.

Use-Case

This enhancement will permit KEDA to maintain workloads at a level desired measured by the rate of message ingress to queues. Thus reducing the tendency of flapping (creation and destruction of pods) as queue backlogs are cleared.
Currently available metrics of messageCountTarget and messageSpoolUseTarget allow KEDA to scale workloads based upon existing backlogs. The new metric allows KEDA to scale workloads based upon the rate of message ingress. This feature has two benefits:

  • Provides a mechanism to maintain performant applications when existing backlogs are small
  • Provides a method to reduce pod "flapping," the continuous creation and destruction of pods, as KEDA maintains workload replicas in concert with observed demand in the form of queue backlogs.

Is this a feature you are interested in implementing yourself?

Yes

Anything else?

No response

@dennis-brinley dennis-brinley added feature-request All issues for new features that have not been committed to needs-discussion labels Jun 8, 2023
@tomkerkhove tomkerkhove added feature-request All issues for new features that have not been committed to feature All issues for new features that have been committed to and removed needs-discussion feature-request All issues for new features that have not been committed to labels Jun 14, 2023
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
Projects
Status: Ready To Ship
Development

Successfully merging a pull request may close this issue.

2 participants