Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upKubernetes pod scaling #2540
Comments
This comment has been minimized.
This comment has been minimized.
|
You could write an alert at which you want to scale (ex: CPU > 80% FOR 10mins). Usage related questions are best limited to: https://groups.google.com/forum/#!forum/prometheus-users |
This comment has been minimized.
This comment has been minimized.
|
Will it work when it recover it should do scale down. Can you please refer any blog or mail thread on this subject. |
This comment has been minimized.
This comment has been minimized.
|
On Tue, Mar 28, 2017 at 4:22 PM, prasenforu ***@***.***> wrote:
Will it work when it recover it should do scale down.
Yes, you can also configure the webhook notifier to send notifications on
resolved alerts. See https://prometheus.io/docs/alerting/configuration/#
<webhook_config>
Can you please refer any blog or mail thread on this subject.
|
This comment has been minimized.
This comment has been minimized.
|
Thanks for response. I am more interested as follows, When cpu high it should trigger one webhook. But when it resolved it should trigger another webhook. Which I am not able to configure. Plesae advice. |
This comment has been minimized.
This comment has been minimized.
|
We don't support different receivers for firing/resolved for the same alert, but you could emulate it with two alerting rules, one that fires when something is bad and one that fires on the opposite condition (everything is good), and then notify different webhooks for each when they are firing. For example:
Not sure how great that pattern is though :) |
This comment has been minimized.
This comment has been minimized.
|
Closing, as questions are for the users mailing list, not GitHub issues. See https://prometheus.io/community/. |
juliusv
closed this
Mar 30, 2017
This comment has been minimized.
This comment has been minimized.
|
If I create another alert for scale down. Like cpu < 70% But in that scenario it is allways true if I do then it will scale down to zero than mean no pod running. My question any alternative approach or does it support alert as range. CPU > 40% but CPU < 70% in a single alert. |
This comment has been minimized.
This comment has been minimized.
andrewhowdencom
commented
Apr 6, 2017
•
|
@prasenforu If you ask your question on the mailing list I may be able to help further. (Paste a link here once you have) |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
prasenforu commentedMar 28, 2017
Recently we tried container monitoring with Prometheus.
Is there any approach where we can scale container/pod using cpu or memory metric in prometheus and alertmanager?