Open sskorobogach opened 1 year ago
DaemonConfig 28|2023-02-26T19:01:33.448Z|INFO|The given daemonAddress () is invalid, using default daemon UDP and TCP address 127.0.0.1:2000.
One possibility could be that your application is unable to talk to the daemon container. The XRay SDK is defaulting to send trace data at 127.0.0.1:2000
whereas I assume that the daemon is in another container with a different address.
You need to configure the SDK with the daemon container's address. Use the env var AWS_XRAY_DAEMON_ADDRESS
to configure it. https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-dotnet-configuration.html#xray-sdk-dotnet-configuration-envvars
HI
I have .Net Core 6.0 web app hosted in the beanstalk env as a docker image. I don't see any batches submitted to the daemon, although everything is configured and started, according to the logs. I have the same issue when I run it locally with a local daemon. But if I'm running the app without the docker, as a usual process, the daemon starts to receive the samples. This gives me an understanding that the SDK configuration is correct. But why it can't reach the daemon from the container?
The app in containers on the local machine has this in the log
EBS logs show only initialization
And no attempts to write the traces. Only this seems to be related.
UdpSegmentEmitter 33|2023-02-26T19:02:02.718Z|DEBUG|UDP Segment emitter endpoint: 127.0.0.1:2000.