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
Is your feature request related to a problem? Please describe.
I'm currently using CloudWatch Container Insights to monitor my k8s clusters. However, I've noticed that the cloudwatch-agent collects metrics from all pods, which increases my CloudWatch Observation Usage costs. In my use case, I want to focus on monitoring specific critical services rather than every pod in the cluster.
For example, I need to monitor pods in certain namespaces or specific pods (like those from a particular deployment) and exclude metrics from less critical ones, such as daemonsets or system pods.
Describe the solution you'd like
I would like the cloudwatch-agent to support filtering metrics based on the Kubernetes namespace and/or pod names. This feature would allow users to specify which namespaces or pods should be monitored, significantly reducing unnecessary metrics and, consequently, CloudWatch costs.
Describe alternatives you've considered
I can't think of an alternative currently.
Additional context
If anyone have any better ideas to reduce Observation costs, please let me know, thanks!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm currently using CloudWatch Container Insights to monitor my k8s clusters. However, I've noticed that the cloudwatch-agent collects metrics from all pods, which increases my CloudWatch Observation Usage costs. In my use case, I want to focus on monitoring specific critical services rather than every pod in the cluster.
For example, I need to monitor pods in certain namespaces or specific pods (like those from a particular deployment) and exclude metrics from less critical ones, such as daemonsets or system pods.
Describe the solution you'd like
I would like the cloudwatch-agent to support filtering metrics based on the Kubernetes namespace and/or pod names. This feature would allow users to specify which namespaces or pods should be monitored, significantly reducing unnecessary metrics and, consequently, CloudWatch costs.
Describe alternatives you've considered
I can't think of an alternative currently.
Additional context
If anyone have any better ideas to reduce Observation costs, please let me know, thanks!
The text was updated successfully, but these errors were encountered: