Bump to version 2.30.0

[Strech]

Added

• Core: Enable libdatadog-based features and tests on macOS ([PROF-13732] Enable testing libdatadog-based features on macOS  #5351)
• Tracing: Add _dd.p.ksr propagated tag to transmit Knuth sampling rate for backend resampling (Add _dd.p.ksr propagated tag for Knuth sampling rate #5436)
• Tracing: Integrations: Add DD_TRACE_<INTEGRATION>_DISTRIBUTED_TRACING environment variables to control distributed tracing per integration (Activate integration-specific distributed tracing config through environment variable #5396)
• Profiling: Add profiler setting experimental_use_system_dns to use system DNS resolver (defaults to true) ([NO-TICKET] Profiling: Add setting to use system dns #5425, [NO-TICKET] Profiling: Use system dns resolver by default #5449)
• Profiling: Allow lowering CPU profiling sampling interval with experimental_cpu_sampling_interval_ms setting ([NO-TICKET] Allow lowering profiling cpu sampling interval #5424)

Changed

• Core: Enable process tags by default by setting DD_EXPERIMENTAL_PROPAGATE_PROCESS_TAGS_ENABLED, expanding tag collection for Tracing, Database Monitoring, Data Streams Monitoring, Profiling, Runtime Metrics, Process Discovery, Remote Configuration, Telemetry, Dynamic Instrumentation, and CrashTracking (enable process tags to true by default #5432)
• Core: Upgrade libdatadog dependency to version 29.0.0 ([PROF-13732] Upgrade libdatadog dependency to version 28.0.2 #5274, [PROF-13732] Upgrade libdatadog dependency to version 29.0.0 #5461)
• Core: Remove dependency on pkg-config system tool for native extension builds ([PROF-7056] Remove dependency on pkg-config system tool for native extension builds #5469)
• Profiling: Improve profiling error message when another profiler is present ([NO-TICKET] Improve profiling error message when another profiler is present #5375)

Fixed

• Tracing: Integrations: Fix endpoint_render.grape ActiveSupport notification instrumentation for grape 3.x ([NO-TICKET] Fix grape endpoint_render for grape 3.x #5414)
• Tracing: Integrations: Fix compatibility with dalli version 5.x and later (Add version 5.x handling for dalli contrib #5435)
• Dynamic Instrumentation: Fix JSON serialization failures when snapshots contain binary data and invalid UTF-8 strings (Fix binary data serialization in dynamic instrumentation #5434)
• Dynamic Instrumentation: Show ERROR probe status when custom serializers produce non-JSON-encodable data instead of silent failures (Add probe status error reporting for snapshot JSON encoding failures #5448)
• Data Streams: Fix Data Streams Monitoring to correctly report the configured environment instead of showing env:none (Add Env field to DSM stats payload #5427)

[github-actions]

👋 Hey @Strech, 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-03-19 09:44:11 UTC}

[ivoanjo]

👍 LGTM

[datadog-official]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 95.13% (-0.02%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 76afc44 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-03-19 10:20:54

Comparing candidate commit 76afc44 in PR branch bump_to_version_2.30.0 with baseline commit 78f9609 in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 46 metrics, 0 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 ----------------------------------'