![](/img/trans.png)
[英]AWS CloudWatch Alarm to add capacity to EC2 autoscaling group has been in alarm forever
[英]CloudWatch custom EC2 memory metric and alarm with AutoScaling policy
我的目标是根据我的EC2实例上使用的内存来测试AutoScaling。
为了监视我的EC2实例内存,我在我的EC2实例上安装了CloudWatch代理,并创建和配置了CloudWatch代理配置文件,如下所示: https ://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch -Agent.html https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/create-cloudwatch-agent-configuration-file.html
{
"metrics": {
"append_dimensions": {
"AutoScalingGroupName": "${aws:AutoScalingGroupName}",
"ImageId": "${aws:ImageId}",
"InstanceId": "${aws:InstanceId}",
"InstanceType": "${aws:InstanceType}"
},
"metrics_collected": {
"cpu": {
"measurement": [
"cpu_usage_idle",
"cpu_usage_iowait",
"cpu_usage_user",
"cpu_usage_system"
],
"metrics_collection_interval": 60,
"totalcpu": false
},
"disk": {
"measurement": [
"used_percent",
"inodes_free"
],
"metrics_collection_interval": 60,
"resources": [
"*"
]
},
"diskio": {
"measurement": [
"io_time"
],
"metrics_collection_interval": 60,
"resources": [
"*"
]
},
"mem": {
"measurement": [
"mem_used_percent"
],
"metrics_collection_interval": 60
},
"swap": {
"measurement": [
"swap_used_percent"
],
"metrics_collection_interval": 60
}
}
}
}
一旦我在EC2实例上启动CloudWatch代理,自定义指标就可以正常工作,并且可以在CloudWatch上看到它们。
sudo /opt/aws/amazon-cloudwatch-agent/bin/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -c ssm:configuration-parameter-store-name -s
我使用此EC2实例创建了AMI,并使用此AMI创建了AutoScaling组。 然后,我基于自定义指标“ mem_used_percent”(> = 50时)设置警报,并将其用作AutoScaling组策略(添加1个实例)。 图片已附上。
我连接到EC2实例,并使用“应力”增加了使用的内存。 发出警报,触发AutoScaling策略,并创建一个新的EC2实例。
我看到的问题是,我在特定的EC2实例而不是整个AutoScaling组上创建警报,并且在终止初始EC2实例后,该警报不再有意义。 除了AutoScaling组,我如何配置相同的想法?
谢谢。
从AWS文档中,
对于CloudWatch代理,您可以使用aggregation_dimensions
聚合自定义指标
"metrics": {
"cpu":{...}
"disk":{...}
"aggregation_dimensions" : [["AutoScalingGroupName"], ["InstanceId", "InstanceType"]]
}
对于仍在使用旧的perl脚本的用户,请检查以下选项:
--aggregated
--auto-scaling
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/mon-scripts.html
我采用了相同的方法,但是没有成功。
{
"metrics": {
"metrics_collected": {
"LogicalDisk": {
"measurement": [
"% Free Space"
],
"metrics_collection_interval": 60,
"resources": [
"*"
]
},
"Memory": {
"measurement": [
"% Committed Bytes In Use"
],
"metrics_collection_interval": 60
},
"Paging File": {
"measurement": [
"% Usage"
],
"metrics_collection_interval": 60,
"resources": [
"*"
]
},
"PhysicalDisk": {
"measurement": [
"% Disk Time"
],
"metrics_collection_interval": 60,
"resources": [
"*"
]
},
"Processor": {
"measurement": [
"% User Time",
"% Idle Time",
"% Interrupt Time"
],
"metrics_collection_interval": 60,
"resources": [
"_Total"
]
}
},
"append_dimensions": {
"ImageId": "${aws:ImageId}",
"InstanceId": "${aws:InstanceId}",
"InstanceType": "${aws:InstanceType}",
"AutoScalingGroupName": "${aws:AutoScalingGroupName}"
},
"aggregation_dimensions" : [["AutoScalingGroupName"]]
}
}
当我在cloudwatch管理控制台中查看输出时,我没有在All> CWAgent下看到AutoScalingGroupName的聚合
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.