DOCS-10681 AWS Lambda Distributed Tracing refresh #29153
Conversation
github-actions
bot
added
Images
Preview links (active after the
|
|
|
||
| {{< partial name="serverless/serverless-apm-recommendations.html" >}} | ||
| ### Supported features | ||
|
|
There was a problem hiding this comment.
I suggest adding a bit of a preview of what Datadog provides for tracing, maybe
| Datadog's libraries for tracing Lambdas provides auto-instrumentation for Lambda invocations and also handles context propagation across managed AWS services and compute that may be upstream or downstream of Lambda functions. |
| }, | ||
| ) | ||
| ``` | ||
| {{< img src="serverless/lambda/tracing/open-trace.png" alt="Your image description" style="width:90%;" >}} |
There was a problem hiding this comment.
suggestion is to add trace map feature in the docs screenshot
|
|
||
| exports.handler = async event => { |
There was a problem hiding this comment.
I suggest adding two more sections here for 'Cold Start Tracing' - blog post here on docs
and 'Sampling traces' (which we talk about in the 'advanced configuration' part of our docs but customers ask about this a lot)
|
|
||
| In Python, you can use the `get_dd_trace_context` helper function to pass tracing context to outgoing events in a Lambda functions: | ||
| In Datadog, the [Serverless > AWS Lambda][5] view displays all of your functions, grouped by service. |
There was a problem hiding this comment.
| In Datadog, the [Serverless > AWS Lambda][5] view displays all of your functions, grouped by service. | |
| In Datadog, the [Serverless > AWS Lambda][5] view displays all of your serverless apps when grouped by service. You can also individually click into a Lambda function. |
|
|
||
| ## Send traces from your serverless application | ||
| {{< img src="serverless/serverless_custom_metrics.png" alt="Architecture diagram for collecting traces, enhanced metrics, custom metrics, and logs from an AWS Lambda application and sending the data to Datadog" >}} | ||
|
|
There was a problem hiding this comment.
We have developed a sample app with our Dev Advocates that allows customers to spin up an example of Datadog here and get them set up https://github.com/DataDog/serverless-sample-app
Is it Ok to link this ?
| - Tracing HTTP requests invoking downstream Lambda functions or containers. | ||
| - Tracing dozens of additional out-of-the-box [Go][9] libraries. |
There was a problem hiding this comment.
Go also supports
- Tracing through API GW, SQS, SNS, Kinesis, EB, Dynamo, and S3
- cold start tracing
| #### Java | ||
|
|
||
| The Datadog Lambda Library and tracing libraries for Java support: | ||
| - Correlation of Lambda logs and traces with trace ID and tag injection. See [Connecting Java logs and traces][10] for more details. |
There was a problem hiding this comment.
Java also supports
-Tracing through API GW, SQS, SNS, Kinesis, EB, Dynamo, and S3
- cold start tracing
| The tracing library for .NET supports: | ||
| {{% /tab %}} | ||
| {{% tab "Go" %}} | ||
| - Manual correlation of Lambda logs and traces with trace ID and tag injection. |
There was a problem hiding this comment.
.NET also supports
Tracing through API GW, SQS, SNS, Kinesis, EB, Dynamo, and S3
cold start tracing
What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes
Outstanding things: