You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Address PR review feedback on AWS Lambda .NET docs
- 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 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: content/en/serverless/aws_lambda/instrumentation/dotnet.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,17 +19,17 @@ further_reading:
19
19
20
20
## Prerequisites
21
21
22
-
Before instrumenting your Lambda function:
22
+
Before you begin, complete these prerequisites:
23
23
24
24
1.**Review compatibility requirements:** See [.NET Core Compatibility](/tracing/trace_collection/compatibility/dotnet-core) for supported .NET versions and integrations.
25
25
2.**Understand Lambda-specific differences:**
26
26
- Uses Lambda layers instead of MSI/system installation
27
-
- Custom instrumentation requires matching layer and NuGet package versions
27
+
- Custom instrumentation requires the NuGet package version to match the Lambda layer version
28
28
- Environment variables are set in Lambda configuration, not system-wide
29
-
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.
29
+
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.
30
30
31
31
<divclass="alert alert-info">
32
-
Looking for traditional host-based setup instead? See <ahref="/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core">Tracing .NET Core Applications</a>.
32
+
Looking for setup on hosts, containers, or Kubernetes instead? See <ahref="/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core">Tracing .NET Core Applications</a>.
33
33
</div>
34
34
35
35
## Setup
@@ -334,7 +334,7 @@ You can then add custom spans and span tags using the .NET tracer. For instructi
334
334
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.
335
335
336
336
**Lambda-specific configuration notes:**
337
-
- Set environment variables in Lambda functionconfiguration,not in code
337
+
- Set environment variables in Lambda functionconfiguration (not through IConfiguration or System.Environment.SetEnvironmentVariable)
338
338
- Some Agent-related settings (like `DD_AGENT_HOST`) are managed by the Datadog Extension
339
339
- Tracer version is determined by the Lambda layer version
0 commit comments