From d48337f173d5b8b6cc92530390aa736d47ff6476 Mon Sep 17 00:00:00 2001 From: Lucas Pimentel Date: Wed, 29 Oct 2025 13:49:30 -0400 Subject: [PATCH 1/2] Add prerequisites and cross-references to AWS Lambda .NET docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a Prerequisites section to help users understand Lambda-specific requirements before they begin setup. Add Configuration and Troubleshooting sections with cross-references to main APM docs. Key additions: - Prerequisites section explaining Lambda-specific differences - Links to .NET Core compatibility requirements - Links to main .NET Core APM docs for background concepts - Configuration section with Lambda-specific notes - Troubleshooting section with diagnostic tool references This improves navigation between Lambda-specific docs and foundational APM documentation, helping users understand how Lambda differs from traditional host-based setups. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../aws_lambda/instrumentation/dotnet.md | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/content/en/serverless/aws_lambda/instrumentation/dotnet.md b/content/en/serverless/aws_lambda/instrumentation/dotnet.md index 388892adca488..61eb3723525bf 100644 --- a/content/en/serverless/aws_lambda/instrumentation/dotnet.md +++ b/content/en/serverless/aws_lambda/instrumentation/dotnet.md @@ -17,6 +17,21 @@ further_reading:
Version 67+ of the Datadog Lambda Extension is optimized to significantly reduce cold start duration. Read more.
+## Prerequisites + +Before instrumenting your Lambda function: + +1. **Review compatibility requirements:** See [.NET Core Compatibility](/tracing/trace_collection/compatibility/dotnet-core) for supported .NET versions and integrations. +2. **Understand Lambda-specific differences:** + - Uses Lambda layers instead of MSI/system installation + - Custom instrumentation requires matching layer and NuGet package versions + - Environment variables are set in Lambda configuration, not system-wide +3. **Learn about .NET tracing:** If you're new to Datadog .NET tracing, read [Tracing .NET Core Applications](/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core) for background concepts. + +
+Looking for traditional host-based setup instead? See Tracing .NET Core Applications. +
+ ## Setup If your application is deployed as a container image, use the _Container Image_ method. @@ -314,6 +329,21 @@ When using the [Datadog Lambda tracing layer for .NET][9], ensure that a second You can then add custom spans and span tags using the .NET tracer. For instructions on how to add spans, see [.NET custom instrumentation][10]. +## Configuration + +Lambda functions support most standard .NET tracer configuration options. See [.NET Core Library Configuration](/tracing/trace_collection/library_config/dotnet-core/) for the full list of environment variables. + +**Lambda-specific configuration notes:** +- Set environment variables in Lambda function configuration, not in code +- Some Agent-related settings (like `DD_AGENT_HOST`) are managed by the Datadog Extension +- Tracer version is determined by the Lambda layer version + +## Troubleshooting + +For common issues and debugging steps, see: +- [.NET Diagnostic Tool](/tracing/troubleshooting/dotnet_diagnostic_tool) +- [Troubleshoot Serverless Monitoring](/serverless/guide/troubleshoot_serverless_monitoring) + ## FIPS compliance {{% svl-lambda-fips %}} From a7f1f83319a008e6e522be1950b5ecf99cd8cd40 Mon Sep 17 00:00:00 2001 From: Lucas Pimentel Date: Wed, 29 Oct 2025 17:00:18 -0400 Subject: [PATCH 2/2] Address PR review feedback on AWS Lambda .NET docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Change "Before instrumenting" to "Before you begin" for direct language - Clarify NuGet version must match Lambda layer version - Remove "you're" contraction per style guide - Replace "traditional host-based" with specific deployment types - Clarify environment variable configuration location 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../en/serverless/aws_lambda/instrumentation/dotnet.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/serverless/aws_lambda/instrumentation/dotnet.md b/content/en/serverless/aws_lambda/instrumentation/dotnet.md index 61eb3723525bf..8e9dc58f41d77 100644 --- a/content/en/serverless/aws_lambda/instrumentation/dotnet.md +++ b/content/en/serverless/aws_lambda/instrumentation/dotnet.md @@ -19,17 +19,17 @@ further_reading: ## Prerequisites -Before instrumenting your Lambda function: +Before you begin, complete these prerequisites: 1. **Review compatibility requirements:** See [.NET Core Compatibility](/tracing/trace_collection/compatibility/dotnet-core) for supported .NET versions and integrations. 2. **Understand Lambda-specific differences:** - Uses Lambda layers instead of MSI/system installation - - Custom instrumentation requires matching layer and NuGet package versions + - Custom instrumentation requires the NuGet package version to match the Lambda layer version - Environment variables are set in Lambda configuration, not system-wide -3. **Learn about .NET tracing:** If you're new to Datadog .NET tracing, read [Tracing .NET Core Applications](/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core) for background concepts. +3. **Learn about .NET tracing:** If new to Datadog .NET tracing, read [Tracing .NET Core Applications](/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core) for background concepts.
-Looking for traditional host-based setup instead? See Tracing .NET Core Applications. +Looking for setup on hosts, containers, or Kubernetes instead? See Tracing .NET Core Applications.
## Setup @@ -334,7 +334,7 @@ You can then add custom spans and span tags using the .NET tracer. For instructi Lambda functions support most standard .NET tracer configuration options. See [.NET Core Library Configuration](/tracing/trace_collection/library_config/dotnet-core/) for the full list of environment variables. **Lambda-specific configuration notes:** -- Set environment variables in Lambda function configuration, not in code +- Set environment variables in Lambda function configuration (not through IConfiguration or System.Environment.SetEnvironmentVariable) - Some Agent-related settings (like `DD_AGENT_HOST`) are managed by the Datadog Extension - Tracer version is determined by the Lambda layer version