Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated X-Ray Lambda function segment section #170

Merged
merged 1 commit into from
Apr 6, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions doc_source/using-x-ray.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,10 @@ From the service map, you can zoom in to see a trace view of your Lambda functio
+ **Attempt** – Represents a single invocation attempt, including any overhead introduced by the Lambda service\. Examples of overhead are time spent initializing the function's code and function execution time\.
+ **Lambda function segment** – Represents execution time for the function for a given invocation attempt\. It starts when the function handler starts executing and ends when the function terminates\. This segment can include three types of subsegments:
+ **Initialization** – The time spent running the `initialization` code of the function, defined as the code outside the Lambda function handler or static initializers\.
+ **Downstream calls** – Calls made to other AWS services from the Lambda function's code\.
+ **Custom subsegments** – Custom subsegments or user annotations that you can add to the Lambda function segment by using the X\-Ray SDK\.
+ **Downstream calls** – Calls made to other AWS services or downstream HTTP requests from the Lambda function's code\.
+ **Custom subsegments** – Custom subsegments that you can add to the Lambda function segment by using the X\-Ray SDK\.

The Lambda function segment is generated by the Lambda service on behalf of the customer. It overwrites any segment created in the Lambda function code, including segments generated by the X-Ray SDK to capture requests via middleware. If a segment is created in Lambda function code, it is implemented as a facade segment. The facade segment only allows custom subsegments to be added to and deleted from it; all other segment operations are treated as no-ops.

**Note**
For each traced invocation, Lambda emits the Lambda service segment and all of its subsegments\. These segments are emitted regardless of the runtime and require you to use the X\-Ray SDK for AWS API calls\.
For each traced invocation, Lambda emits the Lambda service segment and all of its subsegments\. This segment and its subsegments are emitted regardless of the runtime you use\.