X-Ray — Complete Guide
X-Ray — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of AWS Cloud Tutorial on Toolliyo Academy.
On this page
AWS Cloud Tutorial · Lesson 62 of 100
X-Ray
Core services ✓ → Projects
Projects · 2 — Deploy · ~10 min · AWS — Observability & Security
What is this?
AWS X-Ray traces requests across API Gateway, Lambda, ECS, and downstream calls showing latency breakdown and error origins.
Why should you care?
AwsVerse debugs slow checkout by seeing which microservice adds 800 ms in the trace map.
See it live — copy this example
Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).
const AWSXRay = require('aws-xray-sdk-core');
const AWS = AWSXRay.captureAWS(require('aws-sdk'));
exports.handler = AWSXRay.captureAsyncFunc('processOrder', async (event) => {
AWSXRay.captureHTTPsGlobal(require('https'));
return { statusCode: 200, body: 'ok' };
});
What happened?
- X-Ray SDK wraps AWS SDK and HTTPS calls to emit subsegments.
- Enable active tracing on Lambda for automatic service map.
Practice next
- Enable X-Ray on Lambda active tracing.
- Invoke API; open X-Ray service map.
- Find slowest subsegment in trace detail.
- Add custom annotation tenantId on segments.
- Link X-Ray trace to CloudWatch Logs Insights.
Remember
X-Ray = distributed tracing. Service map shows dependencies. Sample traces in high traffic.
AwsVerse checkout trace
p99 checkout latency doubled overnight.
Outcome: X-Ray shows new external tax API adds 600 ms per request.
Interview prep for this lesson
Practice these questions aloud after reading—each links to a full structured answer.
Sign in to ask a question or upvote helpful answers.
No questions yet — be the first to ask!