Setup tags for improved CloudWatch API costing

Hi,

I'm using the 'cwagent-fluent-bit-quickstart.yaml' to monitor / report a number of different EKS clusters into AWS CloudWatch Container Insights which is working really well! However, I've noticed in AWS Cost Explorer I have a high cost of untagged 'MetricStorage:AWS/Logs-EMF' and other API costs, which I think are associated with Container Insights reporting.

Is there a way to use this repo's Helm charts to be able to tag them or at least differentiate the costs between my different clusters so I can accurately report the costs of having each of my environment?

Kind regards,
Oliver

Start with cwagent-fluent-bit-quickstart.yaml and the repository's Helm charts, then trace how Container Insights reports metrics and API usage to AWS CloudWatch. Determine whether resource tags or another supported identifier can differentiate costs for separate EKS clusters in AWS Cost Explorer; done means a documented, working way to attribute those costs.

Written by the indexing model from the issue text.