cloudwatch agent using high disk space

Can you please check the metrics_collection_interval in the configuration file and any wild cards used in the configuration file.

Please ensure you run the latest version of Cloud watch agent as well and try again on this specific instance that you mentioned.

"agent":{
"metrics_collection_interval": 60

To find agent version: "sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a status"

I would recommend to use the document which explains to work with Cloudwatch & Collectd agents together: https://aws.amazon.com/blogs/mt/getting-started-with-cloudwatch-agent-and-collectd/

Hi Anil,

thanks for respond, im using wizard configuration with Basic setup sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-config-wizard

{ "agent": { "metrics_collection_interval": 60, "run_as_user": "cwagent" }, "metrics": { "metrics_collected": { "collectd": { "metrics_aggregation_interval": 60 }, "disk": { "measurement": [ "used_percent" ], "metrics_collection_interval": 60, "resources": [ "*" ] }, "mem": { "measurement": [ "mem_used_percent" ], "metrics_collection_interval": 60 } } } }

nothing seems wrong in my configuration, the problem is my Collectd configuration does collecting so many metric up to 500 files, interface-veth and i dont know where this coming from, there might be a solution to reduce the disk space with remove the files or disable through collectd config file (/etc/collectd/collectd.conf). Need to make sure if any solutions are possible

thanks

Would suggest validating the Collectd Configuration file and review WriteThreads and Aggreation of these metrics along with interval time. Reference links: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-custom-metrics-collectd.html https://aws.amazon.com/blogs/aws/new-cloudwatch-plugin-for-collectd/