Skip to content

Add prerequisites and cross-references to AWS Lambda .NET docs #32477

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.

Sign up for GitHub

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

Draft
wants to merge 2 commits into
base: lpimentel/apm-dotnet-fix-windows-link
Choose a base branch
from
+30 −0
Draft

Add prerequisites and cross-references to AWS Lambda .NET docs #32477

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d48337f
Add prerequisites and cross-references to AWS Lambda .NET docs
lucaspimentel Oct 29, 2025
a7f1f83
Address PR review feedback on AWS Lambda .NET docs
lucaspimentel Oct 29, 2025
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
30 changes: 30 additions & 0 deletions content/en/serverless/aws_lambda/instrumentation/dotnet.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,21 @@ further_reading:

<div class="alert alert-info">Version 67+ of the Datadog Lambda Extension is optimized to significantly reduce cold start duration. <a href="/serverless/aws_lambda/configuration/?tab=datadogcli#using-datadog-lambda-extension-v67">Read more</a>.</div>

## Prerequisites

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 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 new to Datadog .NET tracing, read [Tracing .NET Core Applications](/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core) for background concepts.

<div class="alert alert-info">
Looking for setup on hosts, containers, or Kubernetes instead? See <a href="/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core">Tracing .NET Core Applications</a>.
</div>

## Setup

If your application is deployed as a container image, use the _Container Image_ method.
Expand Down Expand Up @@ -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 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

## 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 %}}
Expand Down
Loading