[DSM] .NET enabled by default

[robcarlan-datadog]

What does this PR do? What is the motivation?

DSM will be enabled by default starting with version 3.22.0 of the tracer. This adds documentation for that, and differences between the default and explicitly enabled state.

Merge instructions

Merge readiness:

• Ready for merge

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

[github-actions]

ℹ️ Documentation Team Review

No documentation team review is required for this pull request.

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/rob.carlan/DSMON-925-net-enabled-by-default/data_streams/setup/language/dotnet

[johannbotha]

Some additional caveats we'll want to mention, I'm not sure exactly how is the best way.

1. A user still needs to pay for DSM for it to be enabled, either through an APM package deal or DSM standalone
2. We do not intend to pass all data that gets to the edge. For example, if a user has 50% data in java tracers and 50% in .NET, we plan to drop all data. We should make that clear here, with an option to reach out to DSM if they want partial .NET data forwarded to DSM backend. (LMK if this doesn't make sense)