instrumentor | Game Boy Music Toy - Music toy for Game Boy | Game Engine library

The X-Ray servlet filter will open a segment when it receives a request and close it before returning a response. The segment it creates represents a full request/response lifecycle. Anything captured as part of serving this request (in this case might be some AWS service calls) is called subsegment. As you can see the subsegments needs the tracing context (which segment is this for).

The issue is that on server startup the instrumentor tries to capture the S3 call but it cannot find the context as there is no request coming in yet. One option is to set an environment variable AWS_XRAY_CONTEXT_MISSING to LOG_ERROR so there is no exception but only a log entry. See more details at https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-java-configuration.html#xray-sdk-java-configuration-envvars.

For running on lambda the lambda container will create a segment for each invocation. It sets the tracing context as environment variable. So as long as the code being captured is within the handler class, the context should always be present.

It's because you are trying to reach a url https and is failing to verify ssl in your case.

Try adding OpenSSL::SSL::VERIFY_PEER = OpenSSL::SSL::VERIFY_NONE

Edit - For Your concern about Man In The Middle Attack

Also You can verify your application by adding an ssl certificate with the following steps

• Download https://curl.haxx.se/ca/cacert.pem into a path_to_file\cacert.pem. Make sure you save it as a .pem file, rather than a text file.

• Set Environment Variable: SSL_CERT_FILE = path_to_file\cacert.pem

• Restart all your ruby / rails applications and the retry accessing it now.

At this time, Amazon API Gateway is not propagating x-amzn-trace-id headers.

It sounds as if your AWS Lambda functions may be deployed behind API Gateway endpoints. Because of this limitation in API Gateway's integration with AWS X-Ray, tracing this operation as one continuous trace will not be possible today.

One approach for tracing this operation in a single continuous trace is having microservice B invoke microservice A directly using the AWS Lambda Invoke API. This API does respect the x-amzn-trace-id header (which would be automatically added to the Invoke request, as you've included the aws-xray-recorder-sdk-aws-sdk-instrumentor artifact in your project).

This is a known problem that has been discussed on the official forum. Here is a couple of links: https://forums.aws.amazon.com/thread.jspa?threadID=252012&tstart=0 https://forums.aws.amazon.com/thread.jspa?threadID=257258&tstart=25

Every time our application attempts to get messages the TracingHandler attempts to create a SubSegment and fails because there is no Segment already created. How can we wrap these requests in a Segment? Wouldn't that information be contained in the message itself to link segments together from the resource that pushed the message to the queue?

The Segment info is kept in a ThreadLocal. You have to create a segment manually if you are running something in a separate thread and thus you'll have the required ThreadLocal data when it creates a subsegment. There is nothing special in the SQS messages and even the SQS service itself related to the X-Ray service. It's only using the SQS client that makes X-Ray infer that a call to SQS has happened by tracking ThreadLocal data with the handlers.

I would have expected there to Context Missing strategy available to create a Segment if one is missing or at least pick up from a parent trace id but I don't see that information contained within their latest docs.

That was one of my feature requests. See the thread with it along with an official answer and along with the current limitation that I found in a try to implement such a Context Missing Strategy myself. https://forums.aws.amazon.com/thread.jspa?threadID=252012&tstart=0