aws / aws/amazon-cloudwatch-agent
Support network filesystems like fsx on diskio metrics in agent configuration file
- Dominant language
- Go
- Stars
- 550
- Forks
- 271
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 13
Description
The "diskio" section does not seem support mount points and only "devices". Network mounted devices like FSX filesystems do not generate metrics, only locally attached nvme partitions. What I am trying to do is collect diskio read_bytes and diskio write_bytes specifically for 3 mounted FSX file systems so that I can monitor the read/write bytes to a specific FSX filesystem from each of our instances. That way I can narrow down which instance is saturating the IO bandwidth for a particular FSX filesystem. However, the metrics collected from the Cloudwatch agent do not provide metrics for those devices.
However, for the disk measurement, this works properly for metrics such as "used_percent" as the disk measurement's resources are mount points instead of devices. When the agent pushes these metrics one of the dimensions is "path" and another is "device" and they are recorded properly. When done with diskio neither "path" nor "device" are recorded, simply "name".
"disk – Optional. Specifies that disk metrics are to be collected. This section is valid only for Linux instances. This section can include as many as two fields:
resources – Optional. Specifies an array of disk mount points. This field limits CloudWatch to collect metrics from only the listed mount points. You can specify * as the value to collect metrics from all mount points. The default value is to collect metrics from all mount points."
"diskio – Optional. Specifies that disk i/o metrics are to be collected. This section is valid only for Linux instances. This section can include as many as two fields:
resources – Optional. If you specify an array of devices, CloudWatch collects metrics from only those devices. Otherwise, metrics for all devices are collected. You can also specify * as the value to collect metrics from all devices."
Contributor guide
Research direction
No file, test, or entry point is named. Start by locating the diskio configuration and metric collection paths, then compare them with the disk mount-point handling described in the issue. Done means diskio read_bytes and write_bytes can target mounted FSX filesystems and emit usable resource dimensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100