Skip to content

Conversation

isker
Copy link

@isker isker commented Aug 27, 2025

Summary

As discussed in #4618, it seems that scaling down these network stats by the number of containers is simply incorrect. On that issue, I have empirically compared EC2 awsvpc numbers to both Fargate awsvpc and EC2 bridge numbers to deduce this.

Implementation details

Don't do that division.

Testing

Existing unit tests were updated.

In terms of validating that this is the correct change, all I have is comparative analysis against existing behaviors of Fargate and EC2 with bridge networking. The only other way I can think to test this is to deploy this to a real EC2 instance and repeat the testing procedure discussed in #4618. I can find no documentation in this project on how to do this. I would appreciate your advice.

New tests cover the changes: no.

Description for the changelog

Bug - Fix undercounting of network stats when using the awsvpc networking mode.

Additional Information

Does this PR include breaking model changes? If so, Have you added transformation functions?
No.

Does this PR include the addition of new environment variables in the README?
No.

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@isker isker requested a review from a team as a code owner August 27, 2025 03:20
As discussed in aws#4618, it seems that scaling down these network stats by
the number of containers is simply incorrect. On that issue, I have
empirically compared EC2 awsvpc numbers to both Fargate awsvpc and EC2
bridge numbers to deduce this.

Fixes aws#4618.
@isker isker force-pushed the fix-ec2-network-stats-undercounting branch from f1694b4 to 2ead5a4 Compare August 27, 2025 03:27
@singholt
Copy link
Contributor

Thanks a lot for reporting the issue and this contribution. We will test your changes, and update here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants