Metrics API
#110
Replies: 1 comment 1 reply
-
|
Thanks for reporting this! I converted it into an issue and I think I already found a fix. Regarding the active TCP connections metric, do you mind creating a separate issue for that? I would need to investigate a bit but what is possible for sure is a metric that shows the timestamp of the last TCP activity. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello! Awesome project, I like it a lot and it has worked exactly as described. Here are some thoughts after using it for a while.
When a pod is scaled to zero, any entries in the metrics API are missing.
I'm trying to combine zeropod with HPA autoscaling on cpu and memory. Please see the below documentation snippet regarding HPA missing metrics:
The result is no scaling decision is made. You could work around this by tuning the scale windows but it would be convenient if the zeropod runtime could fake 0% cpu and memory usage when scaled down. Let me know your thoughts about this.
I'm not too familiar with eBPF but I was also wondering if the number of active TCP connections could be exposed as a metric.
Beta Was this translation helpful? Give feedback.
All reactions