Hi Team,
We have installed ELK monitoring with following beats version
metricbeat version 7.9.0 (amd64), libbeat 7.9.0 [b2ee705fc4a59c023136c046803b56bc82a16c8d built 2020-08-11 19:30:31 +0000 UTC]
packetbeat version
packetbeat version 7.9.0 (amd64), libbeat 7.9.0 [b2ee705fc4a59c023136c046803b56bc82a16c8d built 2020-08-11 19:37:31 +0000 UTC]
heartbeat version
heartbeat version 7.9.0 (amd64), libbeat 7.9.0 [b2ee705fc4a59c023136c046803b56bc82a16c8d built 2020-08-11 19:19:43 +0000 UTC]
but whenever we are enabling the aws module in metricbeat and restarting metricbeat service its getting failed with error.
2022-09-29T07:36:36.242Z INFO [monitoring] log/log.go:131 Stopping metrics logging.
2022-09-29T07:36:36.242Z INFO instance/beat.go:456 metricbeat stopped.
2022-09-29T07:36:36.244Z ERROR instance/beat.go:951 Exiting: 1 error: metricset 'aws/cloudwatch' not found.
sharing aws.yml here
[root@ip-10-.... modules.d]# cat aws.yml
# Module: aws
# Docs: https://www.elastic.co/guide/en/beats/metricbeat/8.4/metricbeat-module-aws.html
- module: aws
period: 5m
metricsets:
- cloudwatch
metrics:
- namespace: AWS/EC2
- namespace: AWS/ElasticMapReduce
#name: ["CPUUtilization", "DiskWriteOps"]
resource_type: ec2:instance
#dimensions:
# - name: InstanceId
# value: i-0686946e22cf9494a
#statistic: ["Average", "Maximum"]
- module: aws
period: 5m
metricsets:
- ec2
- module: aws
period: 24h
metricsets:
- s3_daily_storage
- module: aws
period: 1m
latency: 5m
metricsets:
- s3_request
[root@ip-10-.... modules.d]#
Could you please help here to get working aws.yml here with existing version of metricbeat.