Add EFA Metrics to Container Insights #1941
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
This PR was marked stale due to lack of activity. |
the-mann
added
the
ready for testing
movence
reviewed
Nov 20, 2025
| "container_efa_rdma_read_bytes", | ||
| "container_efa_rdma_write_bytes", | ||
| "container_efa_rdma_write_recv_bytes", | ||
| "container_efa_retrans_bytes", |
Contributor
There was a problem hiding this comment.
also need to update translation test aws/amazon-cloudwatch-agent/translator/tocwconfig/sampleConfig/emf_and_kubernetes_with_gpu_config.yaml
Contributor
There was a problem hiding this comment.
Does emf_and_kubernetes_with_gpu_high_frequency_config.yaml need to be updated too?
Contributor
|
This PR was marked stale due to lack of activity. |
# Conflicts: # go.mod # go.sum
the-mann
force-pushed
the
mpmann/efa-metrics
branch
from
1e5bdf5 to
d3003b2
Compare
movence
previously approved these changes
Dec 11, 2025
duhminick
previously approved these changes
Dec 11, 2025
…EFA retrans metrics - Add container_efa_retrans_bytes, container_efa_retrans_pkts, container_efa_retrans_timeout_events, container_efa_impaired_remote_conn_events, container_efa_unresponsive_remote_events - Add corresponding pod and node EFA retrans metrics - Updates expected config to match recent EFA retrans metrics added in commit 30f0900
- Add container_efa_retrans_bytes, container_efa_retrans_pkts, container_efa_retrans_timeout_events, container_efa_impaired_remote_conn_events, container_efa_unresponsive_remote_events - Add corresponding pod and node EFA retrans metrics to test expectations - Fixes GenerateAwsEmfExporterConfigKubernetesWithHighFrequencyGPUMetrics test failure - Aligns test with EFA retrans metrics added in commit 30f0900
duhminick
approved these changes
Dec 12, 2025
movence
approved these changes
Dec 12, 2025
Contributor
Author
|
most recent commit passing: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/20173265214/job/57914630973 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Blocked on amazon-contributing/opentelemetry-collector-contrib#385 before merging. will update go.mod after that PR has been merged in
Description of the issue
Elastic Fabric Adapter (EFA) is a network interface for Amazon EC2 instances that enables customers to run applications requiring high levels of inter-node communications at scale on AWS. EFA provides lower and more consistent latency and higher throughput than traditional TCP transport, making it ideal for high-performance computing (HPC), machine learning (ML) training, and other distributed workloads.
Currently, the CloudWatch Agent lacks visibility into some new EFA metrics, which are critical for:
Description of changes
This PR adds collection of five key EFA metrics at the node, container, and pod levels:
These metrics are collected from the Linux sysfs interface exposed by the EFA driver and are aggregated at:
The implementation reads hardware counters from the sysfs filesystem and exposes them through the CloudWatch Agent's container insights metrics pipeline.
Tests
Manual Testing:
vpc.amazonaws.com/efa: 1)Testing Configuration:
new integ test: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/19579639336/job/56074086384
The metrics were successfully published to CloudWatch and are queryable with appropriate dimensions (node, pod, container).