We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'd like to know if we could change the behavior of the scaleUp lambda function to integrate the number of message left in the queue as a variable.
Let's consider that I have a stack with a maxSize set to 500, if a queue has 3 messages the stack will scale up to 50 when I need only 3 watcher.
modify
ecs-watchbot/lib/template.js
Lines 778 to 780 in 01a777b
nMessage
maxSize/10
100
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'd like to know if we could change the behavior of the scaleUp lambda function to integrate the number of message left in the queue as a variable.
Let's consider that I have a stack with a maxSize set to 500, if a queue has 3 messages the stack will scale up to 50 when I need only 3 watcher.
How to ?
modify
ecs-watchbot/lib/template.js
Lines 778 to 780 in 01a777b
nMessage
,maxSize/10
and100
.The text was updated successfully, but these errors were encountered: