[EKS] [request]: More CloudWatch Metrics and Configuration
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
**Which service(s) is this request for?**
EKS
**Tell us about your request**
And after setting up and taking a look into the CloudWatch Container Insights for Amazon EKS, I think this is a good way to collect the logs and metrics for Kubernetes. However, I think the CloudWatch Agent is now lack of configurations and metrics to make it more useful. The following is the configurations and metrics that I suggest:
### Configurations
- Ability to select which namespaces to collect the metrics
- Ability to select which app to collect the metrics. The labels could be used for this config, for example: `labels.app` or `labels.k8s-app`
- Ability to select which metrics to collect
### Metrics
- node and pod memory utilization in bytes
- node and pod cpu utilization in mili core
- container memory page faults
- the metrics should collected for separated pods. Now it was collected for deployments, daemon sets... under the name `PodName`. And I think it is not really helpful because the problem can occurs on a single pod of the deployments while the metrics is sum of all the pods.
- The Alarm can be trigger by every single pod of the deployment.
- The health condition of a job or cron-job: number of jobs created, number of the success and failed jobs...
Contributor guide
Assessment
This issue has not been assessed yet.