X-Ray

Question 1

What is the X-Ray Daemon?

Answer 1

A software application that listens for traffic on UDP 2000, receives segment data, and passes it to the X-Ray API

Question 2

Two ways to send trace data to X-Ray (as Segment “documents”)

Answer 2

1. X-Ray Daemon, which will package in batches and send to the SDK
2. Directly through the “PUT TRACE SEGMENTS” API

Question 3

Use case for two Lambda X-Ray-related environmental variables:L XRAY_AMZN_TRACE_ID and AWS_XRAY_CONTEXT_MISSING

Answer 3

_XRAY_AMZN_TRACE_ID: set automatically when X-Ray is enabled

AWS_XRAY_CONTEXT_MISSING: includes values (instructions) that tells the SDK what to do if a downstream tracing header is not present

Question 4

What is a “namespace” in X-Ray, and how does it relate to diagnosing the nature of a trace?

Answer 4

In AWS X-Ray, a “namespace” is a concept that categorizes a segment or subsegment to provide clarity about its type or source. The namespace can be set to:

aws: Indicates the segment or subsegment represents a call to an AWS service.

remote: Indicates the segment or subsegment represents a call to a non-AWS service or any other downstream remote system.

Question 5

X-Ray “BatchGetTraces” versus “GetTraceSummaries” APIs

Answer 5

GetTraceSummaries retrieves summary data about a lot of traces

BatchGetTraces provides more-detailed information, but only about trace(s) you specify.