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
Right now we can only filter based on replication controllers using kube_replication_controller. It is my understanding that ReplicaSet are also included in this.
It would be a lot better if you could filter based on kube_replica_set and/or kube_deployment. Specific metrics for these could prove valuable for monitoring, e.g. the number of pods running for a specific ReplicaSet/Deployment vs. the desired count. All of these values can be extracted from the k8s API.
Another nice addition would be the number of available and unavailable pods. A pod can be running, but not be available. A pod is only available when it's readiness probe succeeds, otherwise it is unavailable. These metrics could be called kubernetes.pods.available and kubernetes.pods.unavailable respectively.
My proposal is to add the following:
kubernetes.pods.desired (for ReplicaSet, Deployments and ReplicationControllers)
kubernetes.pods.available
kubernetes.pods.unavailable
kube_replica_set or/and kube_deployment tags
The addition of these metrics and tags would improve the overall experience with the k8s integration.
The text was updated successfully, but these errors were encountered:
Right now we can only filter based on replication controllers using
kube_replication_controller
. It is my understanding that ReplicaSet are also included in this.It would be a lot better if you could filter based on
kube_replica_set
and/orkube_deployment
. Specific metrics for these could prove valuable for monitoring, e.g. the number of pods running for a specific ReplicaSet/Deployment vs. the desired count. All of these values can be extracted from the k8s API.Another nice addition would be the number of available and unavailable pods. A pod can be running, but not be available. A pod is only available when it's readiness probe succeeds, otherwise it is unavailable. These metrics could be called
kubernetes.pods.available
andkubernetes.pods.unavailable
respectively.My proposal is to add the following:
kubernetes.pods.desired
(for ReplicaSet, Deployments and ReplicationControllers)kubernetes.pods.available
kubernetes.pods.unavailable
kube_replica_set
or/andkube_deployment
tagsThe addition of these metrics and tags would improve the overall experience with the k8s integration.
The text was updated successfully, but these errors were encountered: