kube saturation metrics aren't available for all services
According to our metrics catalog, the following services run on kubernetes, which means we try to generate the following saturation metrics for them:
| Service | kube_horizontalpodautoscaler_desired_replicas | kube_go_memory | kube_pool_cpu | kube_container_cpu | kube_container_memory | kube_pool_max_nodes | kube_node_memory_requests | kube_node_cpu_requests |
|---|---|---|---|---|---|---|---|---|
| web.jsonnet | OK | OK | OK | OK | OK | |||
| git.jsonnet | OK | OK | OK | OK | OK | |||
| consul.jsonnet | OK | OK | ||||||
| camoproxy.jsonnet | ||||||||
| sidekiq.jsonnet | OK | OK | OK | OK | OK | |||
| web-pages.jsonnet | OK | OK | OK | OK | OK | |||
| woodhouse.jsonnet | ||||||||
| registry.jsonnet | OK | OK | OK | OK | OK | |||
| logging.jsonnet | OK | OK | ||||||
| plantuml.jsonnet | OK | OK | OK | |||||
| nginx.jsonnet | OK | |||||||
| websockets.jsonnet | OK | OK | OK | OK | OK | |||
| kas.jsonnet | OK | OK | OK | OK | ||||
| monitoring.jsonnet | OK | OK | ||||||
| mailroom.jsonnet | OK | |||||||
| api.jsonnet | OK | OK | OK | OK | OK | OK |
However, the table shows that we don't have all saturation metrics for all services. We should validate if we need to make sure that we monitor those saturation points for all services, or if it's valid that we don't have metrics for all of them.
Edited by Sean McGivern