Add application-signals routing rules to awsproxy translator
#1979
+15
−0
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.
DO NOT MERGE until amazon-contributing/opentelemetry-collector-contrib#403 is merged and released and dependencies are updated.
Description of the issue
The
awsproxyextension currently routes all requests to X-Ray by default, but we will need to support the new upcoming Application Signals APIs in the future as well.Description of changes
Configure
awsproxyextension to support new Application Signals APIs in the default configuration.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
E2E testing verified:
Ran following command:
./build/bin/linux_amd64/config-translator --input test_config.json --output /tmp/test_cwagent.tomlTest X-Ray routing (default)
curl -X POST http://localhost:2000/GetSamplingRules -d '{}' -H "Content-Type: application/json"Requirements
Before commiting your code, please do the following steps.
make fmtandmake fmt-shmake lintIntegration Tests
To run integration tests against this PR, add the
ready for testinglabel.