- 最新
- 最多得票
- 最多評論
The X-Ray deamon collection happens automatically in the background, provided that you have enabled for the specific lambda, you do not need to send traces to it.
Enabling active tracing with the Lambda API: https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html#services-xray-api
Further information is available here: https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon.html
The AWS X-Ray daemon is a software application that listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the AWS X-Ray API. The daemon works in conjunction with the AWS X-Ray SDKs and must be running so that data sent by the SDKs can reach the X-Ray service. The X-Ray daemon is an open source project. You can follow the project and submit issues and pull requests on GitHub: github.com/aws/aws-xray-daemon
On AWS Lambda and AWS Elastic Beanstalk, use those services' integration with X-Ray to run the daemon. Lambda runs the daemon automatically any time a function is invoked for a sampled request. On Elastic Beanstalk, use the XRayEnabled configuration option to run the daemon on the instances in your environment. For more information, see
相關內容
AWS 官方已更新 3 年前- AWS 官方已更新 1 年前
Unfortunately I don't see how this answers the question. Only the first sentence is your own content. That ‘collection happens automatically’ requires the X-Ray SDK producing traces, which need to be sent. The rest (missing quote formatting) says the daemon ‘listens for traffic on UDP port 2000’ which is already in the question: 127.0.0.1:2000 appears to not leave the container & not reach the X-Ray daemon run outside the container. The question is specifically about Lambda with container image, as without a container image 127.0.0.1:2000 would reach the Lambda daemon AWS starts on our behalf.