Skip to content
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

Xray traces sent by cwa-agent are missing origin value in ECS containers #1466

Open
jwestbrook opened this issue Dec 9, 2024 · 0 comments
Open

Comments

@jwestbrook
Copy link

Describe the bug
We are attempting to swap out the AWS Xray collector to use the CWA agent. Using the aws-xray-sdk node package in our ECS containers the xray traces get stripped of the origin value of "AWS::ECS::Container". So in the Xray Trace Map the ECS Container is seen as a remote node. Additionally we are running the xray collector/cwa-agent container in a separate cluster and setting the daemon endpoint in the aws-xray-sdk setup to send to the other container.

Steps to reproduce
If possible, provide a recipe for reproducing the error.

What did you expect to see?
The ECS Container nodes should be shown as ECS container nodes

What did you see instead?
ECS Container nodes shown as remote nodes.

What version did you use?
Version: 1.300049.1b929

What config did you use?
Config: {"traces": {"traces_collected": {"xray": {"bind_address": "0.0.0.0:2000", "tcp_proxy":{"bind_address":"0.0.0.0:2000" } }, "otlp": {"grpc_endpoint": "0.0.0.0:4317", "http_endpoint": "0.0.0.0:4318" }, "application_signals": {} } }, "logs": {"metrics_collected": {"emf": {}, "application_signals": {} } } }

Environment
OS: AWS ECS AMI amzn2-ami-ecs-hvm-2.0.20241120-x86_64-ebs
Docker: public.ecr.aws/cloudwatch-agent/cloudwatch-agent:latest

Additional context
Add any other context about the problem 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

No branches or pull requests

1 participant