Skip to content

Setup tags for improved CloudWatch API costing #174

Description

@ollieSayer

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions