Bhautik Pipaliya

Thanks for reporting this issue! I would be happy to review PR for this change. I'm marking this issue as enhancement for now.

Hi @rclark , Do you think SDK is using `172.31.133.144` to send data to X-Ray Daemon? I don't think SDK respects DNS TTL in the scenario you mentioned. Why this...

Yes, @rclark I think the part of the reason you're seeing such logs could be because when new ECS containers spins up SDK still used the stale IP address that...

If I understand the question then probably you're asking if SDK should be able to resolve `hostname` of your environment where daemon is running? If that is the case then...

Hi @edwardofclt , This looks like an enhancement. I think this is a reasonable ask. I will add this item in our backlog. Meanwhile, Feel free to contribute and let...

Hi @momotaro98 , I'm not very much familiar with gorm. Looks like X-Ray Go SDK does not support gorm so it won't create automatic subsegment for any calls. So, you...

Hi @aripalo , Thanks for this suggestions. I looked into the code you posted. I believe we can use the below code for opening up a connection and that looks...

Hi @horsewin AWS X-Ray Go SDK does not support gorm instrumentation officially. I think this thread has some workarounds to trace calls with gorm. Looks like you're having issues with...

Hi @vcschapp , Thanks for sharing detailed repro steps. I think one of the reason why there are no trace sent to x-ray could be because of the timeout you...

Hey @a-h, Looks like panic is expected in your code because you're trying to create a subsegment without creating a segment first. Ideally either you should create manual segment using...