aws / aws/amazon-cloudwatch-agent
Add Nvidia GPU uuid report
- Dominant language
- Go
- Stars
- 550
- Forks
- 271
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 13
Description
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently Nvidia GPU metric relies on telegraf and are gathered by Name, Index and Host.
The GPU UUID is available in [telegraf](https://github.com/influxdata/telegraf/blob/master/plugins/inputs/nvidia_smi/README.md ) but excluded in [cloudwatch agent](https://github.com/aws/amazon-cloudwatch-agent/blob/cba127dbb53289239009ea9c761b747d5a2fb57f/translator/translate/metrics/config/deny_list_tags.go#L8)
We'd like to enable AWS Batch customer on ECS/EC2 to monitor their GPU utilization. ECS relies on [GPU UUID for task placement](https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_RunTask.html)
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
The ask is to enable gpu uuid aggregation.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start with the referenced telegraf nvidia_smi README and the cloudwatch agent translator/translate/metrics/config/deny_list_tags.go entry point to understand how GPU UUID is currently excluded. Trace the agent's Nvidia GPU metric aggregation and verify that GPU UUID is available for ECS/EC2 monitoring without losing existing dimensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100