From e604000f7e4d732cde0ea5965d490e3a742f4c98 Mon Sep 17 00:00:00 2001 From: "Austin L." <88366728+AustinLeaming@users.noreply.github.com> Date: Tue, 21 Jan 2025 09:29:53 -0700 Subject: [PATCH 1/2] Update troubleshooting.md Make it more clear on where the debug logs will actually be sent once debug logging is enabled. I've had a few customer reach out about how this is unclear - "how do I send you the debug logs once I've enabled it?". This edit makes it more clear on what will happen once debugging is enabled. --- content/en/serverless/aws_lambda/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/serverless/aws_lambda/troubleshooting.md b/content/en/serverless/aws_lambda/troubleshooting.md index 4f191357b8a9c..b5b293f824d4e 100644 --- a/content/en/serverless/aws_lambda/troubleshooting.md +++ b/content/en/serverless/aws_lambda/troubleshooting.md @@ -39,7 +39,7 @@ To ensure the actual changes made to your Lambda functions are expected, try set ## Collect debugging logs -Enable verbose debugging logs by setting the environment variable `DD_LOG_LEVEL` to `debug` on your Lambda functions. If you are using the [Datadog Forwarder Lambda function][2] for data forwarding from logs, also set `DD_LOG_LEVEL` to `debug` on the Forwarder Lambda function. +Enable verbose debugging logs by setting the environment variable `DD_LOG_LEVEL` to `debug` on your Lambda functions. Debug logs will be sent to the corresponding Lambda function's CloudWatch log group. If you are using the [Datadog Forwarder Lambda function][2] for data forwarding from logs, also set `DD_LOG_LEVEL` to `debug` on the Forwarder Lambda function. If you have issues with tracing, set the environment variable `DD_TRACE_DEBUG` to `true` for extra debugging logs from the Datadog Tracer. From 994480df1b9742faf70e6f7102320c8af0f4b2d8 Mon Sep 17 00:00:00 2001 From: cecilia saixue watt Date: Tue, 21 Jan 2025 12:45:25 -0800 Subject: [PATCH 2/2] Update content/en/serverless/aws_lambda/troubleshooting.md --- content/en/serverless/aws_lambda/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/serverless/aws_lambda/troubleshooting.md b/content/en/serverless/aws_lambda/troubleshooting.md index b5b293f824d4e..9961ecff98602 100644 --- a/content/en/serverless/aws_lambda/troubleshooting.md +++ b/content/en/serverless/aws_lambda/troubleshooting.md @@ -39,7 +39,7 @@ To ensure the actual changes made to your Lambda functions are expected, try set ## Collect debugging logs -Enable verbose debugging logs by setting the environment variable `DD_LOG_LEVEL` to `debug` on your Lambda functions. Debug logs will be sent to the corresponding Lambda function's CloudWatch log group. If you are using the [Datadog Forwarder Lambda function][2] for data forwarding from logs, also set `DD_LOG_LEVEL` to `debug` on the Forwarder Lambda function. +Enable verbose debugging logs by setting the environment variable `DD_LOG_LEVEL` to `debug` on your Lambda functions. Debug logs are sent to the corresponding Lambda function's CloudWatch log group. If you are using the [Datadog Forwarder Lambda function][2] for data forwarding from logs, also set `DD_LOG_LEVEL` to `debug` on the Forwarder Lambda function. If you have issues with tracing, set the environment variable `DD_TRACE_DEBUG` to `true` for extra debugging logs from the Datadog Tracer.