You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I test your tool, I can now decide after N samples for a long time what the average consuming for my components.
Depend on that I can decide what the machine aws type I need, but some times after I scale down the machine some times we face latency issues.
Can we add a new metric to collect samples for requests latency ? so we can compare the average before and after scale down ?
@jatalocks
The text was updated successfully, but these errors were encountered:
Calculating network latency should be part of your Kubernetes networking solution/monitoring. You can see it in the metrics server and export it to prometheus/grafana. This controller is not really suited for that out of the box, it only relates to compute resources. What I can add is timestamps of resizing so you can compare them with latency metrics from your monitoring solution
Hi
After I test your tool, I can now decide after N samples for a long time what the average consuming for my components.
Depend on that I can decide what the machine aws type I need, but some times after I scale down the machine some times we face latency issues.
Can we add a new metric to collect samples for requests latency ? so we can compare the average before and after scale down ?
@jatalocks
The text was updated successfully, but these errors were encountered: