Update document v2.29.0

[dd-apm-ecosystems-autobot]

This is an auto-generated PR to update documentation from here. Please merge (with a merge commit) when ready.\n\nTo resolve conflicts:\nbash\ngit merge release\ngit checkout --ours ..

[github-actions]

👋 Hey @DataDog/ruby-guild, please fill "Change log entry" section in the pull request description.

If changes need to be present in CHANGELOG.md you can state it this way

**Change log entry**

Yes. A brief summary to be placed into the CHANGELOG.md

(possible answers Yes/Yep/Yeah)

Or you can opt out like that

**Change log entry**

None.

(possible answers No/Nope/None)

^{Visited at: 2026-02-20 15:08:37 UTC}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-02-20 15:38:42

Comparing candidate commit 799b3dc in PR branch update-document-v2.29.0 with baseline commit 065545f in branch release.

Found 2 performance improvements and 3 performance regressions! Performance is the same for 39 metrics, 2 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:line instrumentation - targeted

• 🟥 throughput [-16915.539op/s; -16421.203op/s] or [-11.404%; -11.071%]

scenario:line instrumentation - untargeted

• 🟥 throughput [-23071.762op/s; -22935.469op/s] or [-39.235%; -39.003%]

scenario:method instrumentation

• 🟥 throughput [-17464.879op/s; -16663.455op/s] or [-10.164%; -9.698%]

scenario:tracing - Propagation - Datadog

• 🟩 throughput [+2915.556op/s; +3012.450op/s] or [+9.832%; +10.159%]

scenario:tracing - Tracing.log_correlation

• 🟩 throughput [+8949.610op/s; +9317.805op/s] or [+8.700%; +9.058%]

[estherk15]

I know this is preexisting language, but instead of listing when this will be removed, is it possible to update this warning after datadog 3.0.0.0?

Suggested change

This limitation will be removed in `datadog` 3.0.0.