大网数据广告活动
服务器运维问答

CWAgent Disk Space Alarms

· 52CE 我爱测

I'm trying to implement an alarm(in Cloudformation) for disk space free using metrics from the Cloudwatch agent and I'm having issues with devices shuffling DeviceID. I encountered this earlier when working with fstab, EC2 instan…

问题原文

原帖链接 · wronglebowski · CC BY-SA 4.0

I'm trying to implement an alarm(in Cloudformation) for disk space free using metrics from the Cloudwatch agent and I'm having issues with devices shuffling DeviceID.

I encountered this earlier when working with fstab, EC2 instances attach EBS volumes in a seemingly random order. If I have two EBS volumes, one for OS and one for data, they could randomly swap between nvme0n1/nvme1n1. I was able to solve this using partition UUIDs.

However I see no way to work around this when creating alarms. Alarms must be created with metrics that specify the DeviceID(nvme0n1) and the mount point(/var/data). These can swap at any given boot. See https://i.sstatic.net/s9Mbq.jpg You can see there's four data points for effectively two points of information as the devices change when the server reboots.

Is there some way to make Cloudwatch Agent report without the Device or to write the alarm to apply to any Device metric?

已采纳解答

原帖链接 · wronglebowski · CC BY-SA 4.0

After doing some digging in the documentation the solution is to drop the device by using a boolean in the config json file.

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Agent-Configuration-File-Details.html

The resulting block will look like this.

            "disk": {
            "measurement": [
                "used_percent"
            ],
            "metrics_collection_interval": 60,
            "resources": [
                "/",
                "/var/data"
            ],
            "drop_device": true
        },

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-06-09)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。