Add decision trees to .NET Core and Framework APM docs #32476
Closed
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
|
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
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core.md
Outdated
Show resolved
Hide resolved
lucaspimentel
commented
Oct 29, 2025
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core.md
Outdated
Show resolved
Hide resolved
lucaspimentel
commented
Oct 29, 2025
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-framework.md
Outdated
Show resolved
Hide resolved
lucaspimentel
commented
Oct 29, 2025
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-framework.md
Outdated
Show resolved
Hide resolved
lucaspimentel
commented
Oct 29, 2025
content/en/tracing/trace_collection/automatic_instrumentation/dd_libraries/dotnet-core.md
Outdated
Show resolved
Hide resolved
Add "Before you begin" sections with environment-specific decision trees to help users quickly navigate to the correct setup guide for their deployment environment (AWS Lambda, Azure Functions, Azure App Service, Google Cloud Run, or traditional hosts). Key changes: - Add decision tree table at the top of both documents - Replace generic serverless alerts with urgent, specific warnings - .NET Framework version explicitly shows platform limitations (not supported on AWS Lambda, Linux, or Google Cloud Run) - Direct links to all serverless-specific setup guides This prevents users from following incorrect installation steps for serverless environments, which would result in broken instrumentation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
- Replace arrow symbols with "Continue below" for accessibility - Change "you're using" to "If using" for direct, imperative language - Soften "STOP" to "stop:" for more empathetic tone 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
lucaspimentel
force-pushed
the
lpimentel/apm-dotnet-decision-trees
branch
from
9a4474a to
ac00373
Compare
|
Closing this PR. |
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 decision tree tables and prominent warnings to the .NET Core and .NET Framework APM documentation pages to help users quickly identify their deployment environment and navigate to the appropriate setup guide.
Changes:
Motivation:
Users frequently attempt to use the standard APM installation instructions for serverless environments (AWS Lambda, Azure Functions, Azure App Service, Google Cloud Run), which doesn't work and leads to failed installations and support requests. This change catches users at the beginning of their setup journey and routes them correctly.
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 follows the pattern established in the Azure App Service - Windows Code documentation and extends it to the main .NET APM pages.