Add prerequisites and cross-references to AWS Lambda .NET docs #32477
+30
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 29, 2025
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Oct 29, 2025
Preview links (active after the
|
lucaspimentel
commented
Oct 29, 2025
lucaspimentel
commented
Oct 29, 2025
lucaspimentel
commented
Oct 29, 2025
lucaspimentel
commented
Oct 29, 2025
lucaspimentel
commented
Oct 29, 2025
lucaspimentel
commented
Oct 29, 2025
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-lambda-prerequisites
branch
from
d2293ca to
1a4fdd1
Compare
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-decision-trees
branch
from
9a4474a to
ac00373
Compare
lucaspimentel
changed the base branch from
lpimentel/apm-dotnet-decision-trees
to
graphite-base/32477
lucaspimentel
force-pushed
the
graphite-base/32477
branch
from
ac00373 to
dce60f4
Compare
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-lambda-prerequisites
branch
from
1a4fdd1 to
0b1f029
Compare
lucaspimentel
changed the base branch from
graphite-base/32477
to
lpimentel/apm-dotnet-fix-windows-link
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-fix-windows-link
branch
from
ad02060 to
5778445
Compare
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 <noreply@anthropic.com>
- 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>
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-fix-windows-link
branch
from
5778445 to
e7475f2
Compare
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-lambda-prerequisites
branch
from
0b1f029 to
1881ff0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Adds a Prerequisites section and improves cross-referencing between the AWS Lambda .NET documentation and the main .NET Core APM docs.
Changes:
Motivation:
Users coming to the Lambda documentation often lack context about .NET tracing in general or miss important Lambda-specific configuration differences. Similarly, users who land on the main .NET Core docs might be deploying to Lambda but not realize they need different setup instructions. This PR creates better navigation between these related docs and sets proper expectations upfront.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes
This PR complements the decision tree changes in #32476 by ensuring users who reach the Lambda docs understand the prerequisites and can easily navigate back to general .NET tracing docs for conceptual understanding.