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
Limiting the sample size to 1 will cause the pod collector to sample only one pod in the deployment (e.g. at random, or the first responsive one) and use the returned metric, instead of sampling all the pods.
This is useful when pods expose metrics that aren't pod-scoped, but come from a central database or queue system.
Equivalent workaround
Create a Kubernetes Service named e.g. example for the pods exposing the metrics endpoint, and then use it with the external metric collector like this:
Desired behavior
It would be nice to have an option to limit the sample size (i.e. number of sampled pods) for the pod collector:
Limiting the sample size to
1
will cause the pod collector to sample only one pod in the deployment (e.g. at random, or the first responsive one) and use the returned metric, instead of sampling all the pods.This is useful when pods expose metrics that aren't pod-scoped, but come from a central database or queue system.
Equivalent workaround
Create a Kubernetes
Service
named e.g.example
for the pods exposing the metrics endpoint, and then use it with the external metric collector like this:The text was updated successfully, but these errors were encountered: