-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add resource metric integration test #453
base: main
Are you sure you want to change the base?
Conversation
Changes:
|
common.StopAgent() | ||
|
||
// build ListEntitiesForMetric request: | ||
requestBody := []byte(fmt.Sprintf(`{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I think would be nice to turn these into test case input, then in the future if someone else to implement a new test, they can just write an additional case instead of copying this entire boilerplate code. For example: https://github.com/aws/amazon-cloudwatch-agent-test/pull/453/files#diff-13510c6aa10605c1f76162fde322c3a4da1cf75441a3a93cb340fbb9d36c480dR186
Can you attach a new integration test run with this change so we can make sure the test still passes? |
Description of the issue
There is no integration test that verifies that an entity is being sent when we send resource metrics such as cpu and memory to CloudWatch—this is currently a gap in our testing.
Description of changes
ListEntitiesForMetric
to get the entity associated with our metricsListEntitiesForMetric
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Integration test run: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/12838570212