[PROF-13732] Upgrade libdatadog dependency to version 28.0.2 by ivoanjo · Pull Request #5274 · DataDog/dd-trace-rb

ivoanjo · 2026-01-23T16:21:12Z

What does this PR do?

~~This PR bumps the libdatadog dependency from version 25.0.1.1.0 to version ~~26.0.0.1.0~~ 27.0.0.1.0.~~

This PR bumps the libdatadog dependency from version 25.0.1.1.0 to version ~~28.0.0.1.0~~ 28.0.2.1.0.

This new version cleans up the profile exporting API so I've updated our code to match.

Update: It also changes how the sample types get specified, and the format of the crashtracking message.

Also, this will be the first libdatadog version with macOS builds!
(Foreshadowing...)

Motivation:

Adopt latest libdatadog.

Change log entry

Yes. Upgrade libdatadog dependency to version 28.0.2

Additional Notes:

N/A

How to test the change?

Green CI is good, as usual.

ivoanjo · 2026-01-23T17:25:45Z

Hmm we're hitting the packaging limits, I've ping'd @lloeki for help on that one...

datadog-datadog-prod-us1 · 2026-01-23T17:26:06Z

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 95.11% (+0.00%)

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: 1ea1e8d | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!}

pr-commenter · 2026-01-23T17:39:06Z

Benchmarks

Benchmark execution time: 2026-03-02 21:04:41

Comparing candidate commit 1ea1e8d in PR branch ivoanjo/libdatadog-26-ruby with baseline commit f130f04 in branch master.

Found 0 performance improvements and 4 performance regressions! Performance is the same for 40 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:profiling - Allocations ()

🟥 throughput [-175027.883op/s; -168889.023op/s] or [-5.319%; -5.133%]

scenario:profiling - http_transport

🟥 throughput [-390.498op/s; -385.603op/s] or [-14.428%; -14.247%]

scenario:profiling - intern_all 1000 repeated strings

🟥 throughput [-2180.761op/s; -2071.745op/s] or [-8.385%; -7.966%]

scenario:profiling - stack collector (ruby frames - native filenames enabled)

🟥 throughput [-256.222op/s; -253.959op/s] or [-7.545%; -7.478%]

ivoanjo · 2026-01-26T15:01:57Z

Update: We're investigating a possible bug in the profiling reporting code, I'm moving this to draft for now until we confirm it's all good (or else that we need a libdatadog bugfix release)

ivoanjo · 2026-01-30T09:04:39Z

Update we're treating DataDog/libdatadog#1492 and DataDog/libdatadog#1493 as blockers to getting this merged

ivoanjo · 2026-02-05T09:23:53Z

Update:

I've rebased on top of current master + force pushed to clean up the history (it had gotten a bit dirty from updating the gemfiles)
revert(profiling): backend does not use MIME libdatadog#1511 is the current blocker for upgrading to latest libdatadog

ivoanjo · 2026-02-11T16:45:59Z

Update: Libdatadog v27 has now been released. I pushed a commit with the changes needed to make it work, but it's not yet on rubygems -- I tested this on my local machine.

**What does this PR do?** This PR includes the changes documented in the "Releasing a new version to rubygems.org" part of the README: https://github.com/datadog/libdatadog/tree/main/ruby#releasing-a-new-version-to-rubygemsorg **Motivation:** Enable Ruby to use libdatadog v27.0.0. In particular, this will be the first release where we provide macOS binaries for libdatadog on rubygems.org. **Additional Notes:** N/A **How to test the change?** I've tested this change locally with the changes in DataDog/dd-trace-rb#5274 and was able to get a green test suite run for Ruby. As a reminder, new libdatadog releases don't get automatically picked up by dd-trace-rb, so the PR that bumps the dependency will also test this release against all supported Ruby versions.

# What does this PR do? This PR includes the changes documented in the "Releasing a new version to rubygems.org" part of the README: https://github.com/datadog/libdatadog/tree/main/ruby#releasing-a-new-version-to-rubygemsorg # Motivation: Enable Ruby to use libdatadog v27.0.0. In particular, this will be the first release where we provide macOS binaries for libdatadog on rubygems.org. # Additional Notes: N/A # How to test the change? I've tested this change locally with the changes in DataDog/dd-trace-rb#5274 and was able to get a green test suite run for Ruby. As a reminder, new libdatadog releases don't get automatically picked up by dd-trace-rb, so the PR that bumps the dependency will also test this release against all supported Ruby versions. Co-authored-by: ivo.anjo <[email protected]>

ivoanjo · 2026-02-12T11:06:35Z

Almost there! We have an SSI validation failing:

linux-amd64 size 218M exceeds max threshold of 200M

but otherwise we're good to go. Since I've made quite a few changes after the last reviews, I'm going to dismiss them and ask folks again.

Added more changes since

ivoanjo · 2026-02-12T12:56:00Z

Update: Vaccine is failing because of DataDog/libdatadog#1498 so that's not a real issue. We're probably going to remove that spec from vaccine or vaccine entirely as we already have test coverage for this in system-tests (e.g. DataDog/system-tests#6275 )

Strech

LGTM 👍🏼

ivoanjo · 2026-02-20T16:07:47Z

Arghhh there's some internal discussion in the libdatadog channel that v27 might have another regression :(

We should probably hold on this again until we can figure that one out

ivoanjo · 2026-02-23T07:33:16Z

DataDog/libdatadog#1619 is the current blocker :/

gyuheon0h · 2026-02-23T10:08:00Z

chore(crashtracking): use unhandled exception API #5391
[PROF-13732] Upgrade libdatadog dependency to version 28.0.2 #5274 👈 (View in Graphite)
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

# What does this PR do? This PR includes the changes documented in the "Releasing a new version to rubygems.org" part of the README: https://github.com/datadog/libdatadog/tree/main/ruby#releasing-a-new-version-to-rubygemsorg The v28 release is here: https://github.com/DataDog/libdatadog/releases/tag/v28.0.0 # Motivation Enable Ruby to use libdatadog v28.0.0. **IMPORTANT**: this version will not be merged into main for dd-trace-rb as there is a regression in the profiler exporter in v28. However, we still want to release this version as an an effort to keep a running upgrade version ready. # Additional Notes Anything else we should know when reviewing? # How to test the change? I've tested this change locally with the changes in DataDog/dd-trace-rb#5274 and was able to get a green test suite run for Ruby. As a reminder, new libdatadog releases don't get automatically picked up by dd-trace-rb, so the PR that bumps the dependency will also test this release against all supported Ruby versions. Co-authored-by: gyuheon.oh <[email protected]>

# What does this PR do? Packages libdatadog for 28.0.2 gem release. This is useful because this release fixes slow TLS exporter issue that has been delaying [libdatadog upgrade](DataDog/dd-trace-rb#5274) for dd-trace-rb # Motivation What inspired you to submit this pull request? # Additional Notes Anything else we should know when reviewing? # How to test the change? Describe here in detail how the change can be validated. Co-authored-by: gyuheon.oh <[email protected]>

**What does this PR do?** This PR bumps the libdatadog dependency from version 25.0.1.1.0 to version 28.0.2.1.0. This new version cleans up the profile exporting API so I've updated our code to match. Also, this is the first libdatadog version with macOS builds! (Foreshadowing...) **Motivation:** Adopt latest libdadog. **Additional Notes:** N/A **How to test the change?** Green CI is good, as usual. Update lockfiles Bump libdatadog dependency to version 27.0.0 There's a breaking change in profiling (`ddog_prof_ValueType` -> `ddog_prof_SampleType`) + the crashtracking report format changed slightly but otherwise everything looks in good shape. Update lockfiles to use libdatadog 27 [🤖] Lock Dependency: https://github.com/DataDog/dd-trace-rb/actions/runs/21941519831 Update to match libdatadog v27 format for message Minor: Simplify specs Upgrade to v28 [🤖] Lock Dependency: https://github.com/DataDog/dd-trace-rb/actions/runs/22346650666 Bump to 28.0.2.1.0 [🤖] Lock Dependency: https://github.com/DataDog/dd-trace-rb/actions/runs/22583912066

ivoanjo requested review from a team as code owners January 23, 2026 16:21

github-actions bot added the profiling Involves Datadog profiling label Jan 23, 2026

marcotc previously approved these changes Jan 23, 2026

View reviewed changes

lloeki mentioned this pull request Jan 26, 2026

Update one pipeline to add custom OCI package size #5279

Merged

ivoanjo marked this pull request as draft January 26, 2026 15:02

ivoanjo force-pushed the ivoanjo/libdatadog-26-ruby branch from 81b55e3 to 0413bfb Compare February 5, 2026 09:22

Strech previously approved these changes Feb 5, 2026

View reviewed changes

ivoanjo mentioned this pull request Feb 11, 2026

ci(ruby): Package libdatadog v27.0.0 for Ruby [PROF-13732] DataDog/libdatadog#1557

Merged

ivoanjo changed the title ~~[NO-TICKET] Upgrade libdatadog dependency to version 26.0.0~~ [NO-TICKET] Upgrade libdatadog dependency to version 27.0.0 Feb 11, 2026

ivoanjo marked this pull request as ready for review February 12, 2026 09:47

ivoanjo requested review from Strech and marcotc February 12, 2026 11:06

ivoanjo changed the title ~~[NO-TICKET] Upgrade libdatadog dependency to version 27.0.0~~ [PROF-13732] Upgrade libdatadog dependency to version 27.0.0 Feb 12, 2026

ivoanjo mentioned this pull request Feb 12, 2026

[PROF-13732] Enable testing libdatadog-based features on macOS #5351

Merged

p-datadog approved these changes Feb 12, 2026

View reviewed changes

lloeki mentioned this pull request Feb 12, 2026

Remove vaccine from CI #5354

Merged

lloeki mentioned this pull request Feb 12, 2026

Reduce SSI image size #5352

Merged

marcotc approved these changes Feb 13, 2026

View reviewed changes

Strech approved these changes Feb 16, 2026

View reviewed changes

ivoanjo marked this pull request as draft February 23, 2026 07:33

gyuheon0h force-pushed the ivoanjo/libdatadog-26-ruby branch from d2c6ffa to b5a8d2f Compare February 23, 2026 10:07

gyuheon0h mentioned this pull request Feb 23, 2026

chore(crashtracking): use unhandled exception API #5391

Closed

gyuheon0h force-pushed the ivoanjo/libdatadog-26-ruby branch from c64957e to b5a8d2f Compare February 23, 2026 10:17

gyuheon0h mentioned this pull request Feb 23, 2026

ci(ruby): Package libdatadog v28.0.0 for Ruby DataDog/libdatadog#1621

Merged

gyuheon0h changed the title ~~[PROF-13732] Upgrade libdatadog dependency to version 27.0.0~~ [PROF-13732] Upgrade libdatadog dependency to version 28.0.0 Feb 23, 2026

gyuheon0h force-pushed the ivoanjo/libdatadog-26-ruby branch from 29113a3 to 30c93b0 Compare February 24, 2026 12:39

gyuheon0h mentioned this pull request Mar 2, 2026

chore(ruby): package libdatadog for 28.0.2 DataDog/libdatadog#1639

Merged

gyuheon0h force-pushed the ivoanjo/libdatadog-26-ruby branch from 30c93b0 to 31e40be Compare March 2, 2026 15:53

gyuheon0h changed the title ~~[PROF-13732] Upgrade libdatadog dependency to version 28.0.0~~ [PROF-13732] Upgrade libdatadog dependency to version 28.0.2 Mar 2, 2026

gyuheon0h marked this pull request as ready for review March 2, 2026 15:54

gyuheon0h force-pushed the ivoanjo/libdatadog-26-ruby branch 2 times, most recently from 5ca940e to 913e09d Compare March 2, 2026 18:45

gyuheon0h force-pushed the ivoanjo/libdatadog-26-ruby branch from 913e09d to 9330399 Compare March 2, 2026 18:47

Merge branch 'master' into ivoanjo/libdatadog-26-ruby

1ea1e8d

gyuheon0h merged commit 158e037 into master Mar 2, 2026
933 of 939 checks passed

gyuheon0h deleted the ivoanjo/libdatadog-26-ruby branch March 2, 2026 21:34

github-actions bot added this to the 2.30.0 milestone Mar 2, 2026

gyuheon0h mentioned this pull request Mar 2, 2026

Use unhandled exception API #5411

Merged

Strech mentioned this pull request Mar 19, 2026

Bump to version 2.30.0 #5474

Merged

Conversation

ivoanjo commented Jan 23, 2026 • edited by gyuheon0h Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ivoanjo commented Jan 23, 2026

Uh oh!

datadog-datadog-prod-us1 bot commented Jan 23, 2026 • edited by datadog-official bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pr-commenter bot commented Jan 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Explanation

More details about the CI and significant changes

scenario:profiling - Allocations ()

scenario:profiling - http_transport

scenario:profiling - intern_all 1000 repeated strings

scenario:profiling - stack collector (ruby frames - native filenames enabled)

Uh oh!

ivoanjo commented Jan 26, 2026

Uh oh!

ivoanjo commented Jan 30, 2026

Uh oh!

ivoanjo commented Feb 5, 2026

Uh oh!

ivoanjo commented Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ivoanjo commented Feb 12, 2026

Uh oh!

ivoanjo commented Feb 12, 2026

Uh oh!

Strech left a comment

Choose a reason for hiding this comment

Uh oh!

ivoanjo commented Feb 20, 2026

Uh oh!

ivoanjo commented Feb 23, 2026

Uh oh!

gyuheon0h commented Feb 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

ivoanjo commented Jan 23, 2026 •

edited by gyuheon0h

Loading

datadog-datadog-prod-us1 bot commented Jan 23, 2026 •

edited by datadog-official bot

Loading

pr-commenter bot commented Jan 23, 2026 •

edited

Loading

ivoanjo commented Feb 11, 2026 •

edited

Loading

gyuheon0h commented Feb 23, 2026 •

edited

Loading