Serverless AWS Lambda Development · 课时

使用 AWS X-Ray 进行分布式追踪

使用 AWS X-Ray 实现并分析分布式追踪，可视化请求在无服务器架构中的流转，并定位性能瓶颈。

使用 AWS X-Ray 进行分布式追踪 是 CoddyKit 上的免费 Serverless AWS Lambda Development 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Serverless AWS Lambda Development 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Serverless AWS Lambda Development 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Tracing Serverless Requests

In serverless applications, a single user request often travels through many services, like an API Gateway, multiple Lambda functions, and databases. Understanding this journey can be complex!

This is where distributed tracing comes in. It's a technique to track a request as it flows across these different services, providing a complete end-to-end view.

Meet AWS X-Ray

AWS X-Ray is a service that helps developers analyze and debug distributed applications built using microservices. It provides an end-to-end view of requests as they travel through your application.

With X-Ray, you can:

Visualize service interactions.
Identify performance bottlenecks.
Debug errors across distributed systems.

X-Ray Segments Explained

The basic unit of data in X-Ray is a segment. Each service (like a Lambda function or an API Gateway) that's part of your application sends its own segment to X-Ray.

A segment contains information about the work done by that service, including:

The service's name and ID.
Details about the incoming request.
Timing information (start and end times).
Any errors or faults that occurred.

Deeper Dive: Subsegments

Within a service's segment, you can create subsegments for more detailed tracing. Subsegments represent discrete units of work within that service.

For example, a Lambda function's segment might contain subsegments for:

Calls to a database (like DynamoDB).
HTTP requests to an external API.
Specific business logic within your code.

They help pinpoint exactly where time is being spent inside a service.

Traces and The Service Map

All segments and subsegments generated by a single request are grouped together to form a trace. This trace provides a complete, end-to-end view of the request's journey.

X-Ray then uses these traces to generate a service map. This is a visual representation of your application's components and the connections between them, showing latency and error rates.

Enable X-Ray for Lambda

To start tracing your Lambda functions, you first need to enable X-Ray tracing for them. This can be done easily through the AWS Management Console or via Infrastructure as Code (like AWS SAM or CloudFormation).

In the Console:

Go to your Lambda function.
Under 'Configuration', select 'Monitoring and operations tools'.
Edit and enable 'Active tracing' for AWS X-Ray.

This sets up Lambda to send basic function invocation data to X-Ray.

Instrument Python Lambda Code

While enabling X-Ray captures basic data, for deeper insights (like custom subsegments or tracing non-AWS SDK calls), you need to instrument your code using the X-Ray SDK.

Here's a Python example:

from aws_xray_sdk.core import xray_recorder
from aws_xray_sdk.core import patch_all

# Patch all AWS SDK calls automatically
patch_all()

def lambda_handler(event, context):
    # Start a custom subsegment for specific logic
    with xray_recorder.in_subsegment('## my_custom_logic'):
        print("Executing custom business logic...")
        # Simulate some work
        import time
        time.sleep(0.05)

    # Any AWS SDK calls after patch_all() will be automatically traced.
    # For example, a DynamoDB put_item() call.

    return {
        'statusCode': 200,
        'body': 'Hello from Lambda with X-Ray!'
    }

# For local testing (not typically deployed with Lambda)
if __name__ == '__main__':
    print(lambda_handler({}, {}))

Instrument Node.js Lambda Code

Similarly, for Node.js Lambda functions, you use the aws-xray-sdk package to instrument your code. This allows you to capture custom subsegments and ensure AWS SDK calls are traced.

Here's a Node.js example:

const AWSXRay = require('aws-xray-sdk');

// Patch all AWS SDK calls automatically.
// This ensures calls to other AWS services are traced.
AWSXRay.captureAWS(require('aws-sdk'));

exports.handler = async (event, context) => {
    // Get the current segment created by Lambda's X-Ray integration.
    const segment = AWSXRay.getSegment();

    // Create a custom subsegment to trace specific logic.
    if (segment) { // Ensure segment exists for safe local execution
        const customSubsegment = segment.addNewSubsegment('## MyCustomLogic');
        try {
            console.log("Executing custom business logic...");
            await new Promise(resolve => setTimeout(resolve, 50)); // Simulate work
        } finally {
            customSubsegment.close();
        }
    } else {
        console.log("X-Ray segment not found, executing without tracing.");
        await new Promise(resolve => setTimeout(resolve, 50)); // Simulate work
    }

    return {
        statusCode: 200,
        body: JSON.stringify('Hello from Lambda with X-Ray!'),
    };
};

// For local execution, you can simulate a call to the handler.
if (require.main === module) {
    console.log("Running handler locally...");
    exports.handler({}, {}).then(result => console.log(result));
}

Reading the Service Map

Once X-Ray collects trace data, you can view the service map in the X-Ray console. This map visually represents your application's components as nodes and their interactions as edges.

Look for:

Nodes: Represent services (Lambda, API Gateway, DynamoDB).
Edges: Show connections and data flow between services.
Colors: Indicate service health (green for healthy, red for errors).
Latency: Visual cues and metrics on edges show request duration.

Pinpointing Bottlenecks

The real power of X-Ray is in identifying performance issues. By examining a trace's timeline, you can see how long each segment and subsegment took to complete.

This helps you:

Identify slow services: Which service is taking the most time?
Find inefficient code: Which subsegment within a function is causing delays?
Detect external dependencies: Is a third-party API call or database query slowing things down?

X-Ray Tracing Check

Let's test your understanding of AWS X-Ray's capabilities.

Tracing the Path Forward

Congratulations! You've learned how AWS X-Ray provides invaluable visibility into your serverless applications.

By enabling X-Ray, instrumenting your code, and interpreting the service map and trace timelines, you can effectively:

Understand complex request flows.
Diagnose latency issues and errors.
Optimize your application's performance.

Embrace X-Ray to build more robust and performant serverless systems!

常见问题解答

「使用 AWS X-Ray 进行分布式追踪」课时是免费的吗？

是的 — 「使用 AWS X-Ray 进行分布式追踪」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Serverless AWS Lambda Development 课程的其余内容，请升级到 CoddyKit PRO。 Serverless AWS Lambda Development 课程共包含 4 节课。

「使用 AWS X-Ray 进行分布式追踪」这节课中我会学到什么？

使用 AWS X-Ray 实现并分析分布式追踪，可视化请求在无服务器架构中的流转，并定位性能瓶颈。你通过在浏览器中直接运行的动手代码来练习 Serverless AWS Lambda Development，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Serverless AWS Lambda Development 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Serverless AWS Lambda Development 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「使用 AWS X-Ray 进行分布式追踪」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Serverless AWS Lambda Development 课中编写并运行代码吗？

能。每节 Serverless AWS Lambda Development 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Serverless AWS Lambda Development