From 6fd84c171cd488204a6a8b1f4764fccd8e148cda Mon Sep 17 00:00:00 2001 From: Ryan Strat Date: Fri, 22 May 2026 16:35:59 -0400 Subject: [PATCH] Address followup feedback on X-Ray docs Address two late review comments on PR #36946: - Glossary: trace merging with Lambda now describes both upstream and downstream merging, matching the linked merge-step-functions -lambda page. - connect_invoking_resources: drop the X-Ray fallback parenthetical so the page no longer nudges readers toward X-Ray when the Lambda Extension is the recommended path. --- content/en/serverless/glossary/_index.md | 2 +- content/en/serverless/guide/connect_invoking_resources.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/content/en/serverless/glossary/_index.md b/content/en/serverless/glossary/_index.md index 2113dddb33a..bdfcd28dd8c 100644 --- a/content/en/serverless/glossary/_index.md +++ b/content/en/serverless/glossary/_index.md @@ -98,7 +98,7 @@ AWS Step Functions is a serverless orchestration service from Amazon Web Service |---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | [Step Functions monitoring][2] | Datadog's offering for monitoring AWS Step Functions, including tracing, logs, and enhanced metrics. | | [Enhanced Step Functions metrics][3] | Metrics that go beyond the default CloudWatch metrics for Step Functions. Enhanced Step Functions metrics are in the `aws.states.enhanced.*` namespace. | -| [Trace merging with Lambda][4] | Datadog merges AWS Step Functions traces with downstream AWS Lambda traces into a single, connected trace. | +| [Trace merging with Lambda][4] | Datadog merges AWS Step Functions traces with upstream and downstream AWS Lambda traces into a single, connected trace. | | [Distributed Map tracing][5] | Tracing for large-scale parallel workloads run with Distributed Map states. | | [Redrive support][6] | Datadog supports tracing for redriven Step Function executions. | diff --git a/content/en/serverless/guide/connect_invoking_resources.md b/content/en/serverless/guide/connect_invoking_resources.md index 087179d79a4..80ca19e34d2 100644 --- a/content/en/serverless/guide/connect_invoking_resources.md +++ b/content/en/serverless/guide/connect_invoking_resources.md @@ -15,11 +15,10 @@ To instrument your Lambda functions for the first time, follow the [serverless i Managed resources are automatically connected to your AWS Lambda functions if all of the following are true: - Your functions are written in Node.js or Python Lambda runtimes. -- [APM with Datadog SDKs (`dd-trace`)][2] is configured on your functions. (Existing X-Ray users can alternatively configure [APM with Datadog's X-Ray integration][2] and [enrich AWS X-Ray segments with Datadog's Lambda Library][3].) +- [APM with Datadog SDKs (`dd-trace`)][2] is configured on your functions. - The managed resource invoking your function is one of the following: API Gateway, SQS, SNS, EventBridge, Kinesis, DynamoDB, S3. - Your functions are instrumented with a recent version of Datadog's Lambda Library (>= `v3.46.0` for Node, >= `v28` for Python). [1]: /serverless/installation [2]: /serverless/distributed_tracing#choose-your-tracing-library -[3]: /integrations/amazon_xray/#enriching-xray-segments-with-datadog-libraries [4]: https://app.datadoghq.com/functions \ No newline at end of file