-
Notifications
You must be signed in to change notification settings - Fork 30
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
[APM] High Cardinality: Integration testing #355
Closed
Closed
Conversation
This file contains 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
* add auto_removal test cases
majanjua-amzn
force-pushed
the
apm
branch
2 times, most recently
from
October 6, 2023 17:40
c98e329
to
768e7be
Compare
* adding mock http server * added testing to httpserver * added graceful shutdown * added check data * added certificates for https Co-authored-by: name <[email protected]> * Merge main to traces-performance-test (aws#3) * Upgrade EKS Version and Fix EKS EMF Log JSON (aws#329) * Multi-System Trace Integration Test (aws#318) Co-authored-by: Jeffrey Chien <[email protected]> --------- Co-authored-by: Seth L <[email protected]> Co-authored-by: Jeffrey Chien <[email protected]> * added xray performance test * generating traces * PR Cleanup (aws#6) * trying docker * PR Cleanup * alternative optional mock server start * merging docker branch * Restructed Xray Test --------- Co-authored-by: name <[email protected]> Co-authored-by: Seth L <[email protected]>
* AppSignals Metrics and Traces Integration test --------- Co-authored-by: Lisa Guo <[email protected]> Co-authored-by: Lisa Guo <[email protected]>
majanjua-amzn
force-pushed
the
apm
branch
2 times, most recently
from
October 30, 2023 23:29
b6333f7
to
858219d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The implemented tests ensure that a user can change the configuration of CW agent to drop, keep, or replace certain metrics. There is one test case implemented for each of these possibilities and these run in parallel like the other test cases.
The reason for these being separate from the existing default case is that they each require a different CW agent configuration.
Current problem:
Adding the configuration causes the values of each metric not to show up
Example:
Default case (working): link
Drop: link
Keep: link
Replace: link
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
Ran the integration test workflow in CW agent repo here