chore(libdatadog): turn on collecting all threads#5724
Conversation
|
👋 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-05-11 12:49:56 UTC |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
fed7238 to
a48acfe
Compare
BenchmarksBenchmark execution time: 2026-05-11 13:33:31 Comparing candidate commit a0e8581 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 45 metrics, 1 unstable metrics.
|
🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: a0e8581 | Docs | Datadog PR Page | Give us feedback! |

What does this PR do?
Crashtracking now allows collection of all threads for crash reports. We should turn it on.
Motivation:
Change log entry
N/A
Additional Notes:
How to test the change?