feat(publish-metrics): implement tracing for the cloudwatch reporter #2555
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.
Description
Implementing tracing support for the Cloudwatch reporter. The reporter will use OpenTelemetry reporter in the background for tracing, and traces will be exported to AWS X-Ray.
Configuration
Cloudwatch agent (or ADOT) installation is required for local runs, but for Fargate runs the ADOT sidecar will be dynamically configured to send traces to AWS X-Ray.
Testing
Unit tests added on
publish-metrics
side and an e2e test added on thecli
sideNotes
Important: Users that wish to use this feature with Fargate runs and had already ran Artillery tests on Fargate in the past will need to delete the
'artilleryio-ecs-worker-role'
IAM role and the'artilleryio-ecs-worker-policy'
IAM policy from their account prior to running tests in order for this feature to work. This is needed because the role will have to be recreated with the necessary permissions to send traces to AWS X-RayThis is a new clean branch for feat(publish-metrics): implement tracing support for cloudwatch reporter #2487
Pre-merge checklist