Thanks for the update...
On Wed, Sep 13, 2017 at 5:13 PM, Clayton Coleman
wrote:
> Custom metrics autoscaling is coming soon. It will be based on prometheus
> metrics exposed by your app.
>
> On Sep 13, 2017, at 7:33 AM, Josef Karasek wrote:
>
> At Promcon [0] I talked with a guy who exposes so
Cool, we did experiment with Prometheus metrics based on a number of
messages in SQS but we were not able to set it as auto scaling condition.
So do you have any estimate when we can expect auto scaling based on custom
metrics?
On Wed, Sep 13, 2017 at 1:43 PM, Clayton Coleman
wrote:
> Custom met
Custom metrics autoscaling is coming soon. It will be based on prometheus
metrics exposed by your app.
On Sep 13, 2017, at 7:33 AM, Josef Karasek wrote:
At Promcon [0] I talked with a guy who exposes some metrics (https
connections, sql queries) in the prometheus format [1].
People also use JMX
At Promcon [0] I talked with a guy who exposes some metrics (https
connections, sql queries) in the prometheus format [1].
People also use JMX (for you that would probably be Jolokia?) and expose
metrics that way[2]. That's how you should be
able to reach the queue size etc. But I have to say, I ha
Hi,
We are Fabric8 Analytics team, trying to scale workers (OSD containers)
up/down based on incoming user traffic. Based on research done so far,
there is no easy way to scale up / down (OpenShift) based on some metric
'like number of messages in a queue'.
Here is the issue being tracked:
