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

Latency Metric #34

Open
wmashal opened this issue Jun 17, 2023 · 2 comments
Open

Latency Metric #34

wmashal opened this issue Jun 17, 2023 · 2 comments

Comments

@wmashal
Copy link

wmashal commented Jun 17, 2023

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

@amitai-devops
Copy link
Collaborator

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

@devevarde
Copy link

@amitai-devops The timestamp also help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants