X-Ray Advantages
- Troubleshooting performance
- understand dependencies in microservice
- pinpoint service issues
- review request behavior
- find error and exceptions
- meeting SLA times
- where I am throttled
- identify users that are impacted
X-Ray Enablement
- Install the X-Ray Daemon Or enable AWS Integration
- each application must have IAM right to right data to X-ray
- AWS Lambda and other services run X-Ray
- X-Ray daemon works a low level UDP packet interceptor
X-Ray Instrumentation
- Instrumentation: means the measure of production performance, diagnose errors, and to write trace information
- to instrument your application code, use the X-Ray SDK
X-Ray: Segments
Each application / service will send them
X-Ray: Subsegments
If you need more details in your segment
X-Ray: Trace
Segments collected together from an end-to-end trace
X-Ray: Sampling
Decrease the amount of requests sent to X-Ray, reduce cost
X-Ray: Annotations
Key Value pairs used to index traces and use with search filters
X-Ray: Metadata
Key Value pairs NOT indexed, NOT used for searching
X-Ray: Sampling Rules
- you control the amount of data you record
- you can modify sampling rules without changing your code
- be default the x-ray SDK records the first request each second and 5% of any additional requests
- one request per second is the reservoir which ensure that at least one trace is recorded each second as long as the is service requests
X-Ray: GetServiceGraph
Main graph
X-Ray: BatchGetTraces
Retrieves a list of traces specified by ID
X-Ray: GetTraceSummaries
Retrieves IDs and annotations for traces available for a specific time
X-Ray: GetTraceGraph
Retrieves a service graph for one or more specific trace
X-Ray: Elastic Beanstalk
- Beanstalk includes the X-Ray daemon
- set option in console or with configuration file (in .ebextenstions/X-ray-daemon.config)
- application code is instrumented with x-ray SDK
NOTE: X-ray Daemon not provided for Multcontainer Docker
X-Ray: ECS Integration Options
- Container as a Daemon: runs on the EC2 cluster where applications are running
- Container as a Side Car: runs right next to the application
X-Ray: Task Definition
- Containers must be linked at the network layer by the ports.
- Container w/ Daemon works on port 2000
- Container w/ App has an Environment variable AWS_XRAY_DAEMON_ADDRESS with the value: X-ray-daemon:2000
Which of the following does NOT help you with debugging?
- X-Ray Daemon
- X-Ray Sampling
- EC2 Instance Role
- CloudTrail
- X-Ray Sampling
It’s a sampling algorithm to determine which requests get traced.
