refactor(rc)!: make conversion from RemoteConfigProduct back and forth generally available

[bwoebi]

In wasm we need to shuffle these around via string repr, hence simply use strum to expose this.

Renaming the enum values to be more canonical.

[datadog-datadog-us1-prod]

⚠️ Autotest was unable to complete this review. View session

Please try again by commenting @autotest review.

[bwoebi]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-06 14:40:31 UTC ℹ️ Start processing command /merge

---

2026-08-06 14:40:38 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

• Run /code blockers to see what is blocking it.
• Run /remove to cancel it.

---

2026-08-06 15:14:27 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 50m (p90).

---

2026-08-06 16:01:09 UTC ❌ MergeQueue: The checks failed on this merge request

Tests failed on this commit 69f7a74:

• run-miri (1)
• run-miri (5)
• allchecks

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

[datadog-datadog-us1-prod]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 80.00%
• Overall Coverage: 75.82%

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 08be668 | Docs | Datadog PR Page | Give us feedback!}

[pr-commenter]

Benchmarks

Comparison

Benchmark execution time: 2026-08-07 04:29:59

Comparing candidate commit 08be668 in PR branch bob/strum-rc-enum with baseline commit 05d785e in branch main.

Found 9 performance improvements and 1 performance regressions! Performance is the same for 130 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 ----------------------------------'

scenario:tags/replace_trace_tags

• 🟥 execution_time [+104.831ns; +118.240ns] or [+4.434%; +5.001%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_4/8

• 🟩 execution_time [-18.680ns; -18.481ns] or [-4.550%; -4.501%]

scenario:vec_map/insert/128

• 🟩 execution_time [-1.134µs; -1.126µs] or [-31.005%; -30.785%]
• 🟩 throughput [+15577139.237op/s; +15718084.215op/s] or [+44.517%; +44.920%]

scenario:vec_map/insert/16

• 🟩 execution_time [-143.795ns; -141.127ns] or [-24.881%; -24.420%]
• 🟩 throughput [+8971641.350op/s; +9150746.654op/s] or [+32.401%; +33.048%]

scenario:vec_map/insert/64

• 🟩 execution_time [-564.289ns; -560.214ns] or [-29.844%; -29.629%]
• 🟩 throughput [+14265293.247op/s; +14390627.336op/s] or [+42.144%; +42.514%]

scenario:vec_map/insert/8

• 🟩 execution_time [-73.689ns; -72.914ns] or [-25.014%; -24.751%]
• 🟩 throughput [+8950186.626op/s; +9040894.357op/s] or [+32.956%; +33.290%]

Benchmark execution time: 2026-08-07 04:28:38

Comparing candidate commit 08be668 in PR branch bob/strum-rc-enum with baseline commit 05d785e in branch main.

Found 0 performance improvements and 1 performance regressions! Performance is the same for 88 metrics, 10 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:datadog_sample_span/resource_pattern_rule_not_matching/wall_time

• 🟥 execution_time [+12.359ns; +12.476ns] or [+7.755%; +7.828%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

[dd-octo-sts]

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.19 MB	89.19 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.20 MB	8.20 MB	0% (0 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.06 MB	11.06 MB	0% (0 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.37 MB	100.37 MB	0% (0 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.63 MB	26.63 MB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	191.42 MB	191.43 MB	+0% (+8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	1001.53 MB	1001.58 MB	+0% (+52.54 KB) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.71 MB	8.71 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.62 MB	25.62 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.01 MB	51.01 MB	0% (0 B) 👌

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.22 MB	23.22 MB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	196.32 MB	196.33 MB	+0% (+8.00 KB) 👌
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	990.59 MB	990.64 MB	+0% (+51.86 KB) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.73 MB	6.73 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.55 MB	27.55 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.55 MB	48.55 MB	0% (0 B) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.47 MB	79.47 MB	0% (0 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.13 MB	9.13 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.12 MB	95.12 MB	0% (0 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.14 MB	11.14 MB	0% (0 B) 👌

[bwoebi]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-06 16:01:57 UTC ℹ️ Start processing command /merge

---

2026-08-06 16:02:03 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 50m (p90).

---

2026-08-06 16:46:54 UTC ⚠️ MergeQueue: This merge request build was cancelled

bob.weinand@datadoghq.com cancelled this merge request build

[bwoebi]

/merge -c

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-06 16:46:44 UTC ℹ️ Start processing command /merge -c

[bwoebi]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-07 03:03:33 UTC ℹ️ Start processing command /merge

---

2026-08-07 03:03:39 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

• Run /code blockers to see what is blocking it.
• Run /remove to cancel it.

---

2026-08-07 03:58:31 UTC ⚠️ MergeQueue: This merge request was unqueued

levi.morrison@datadoghq.com unqueued this merge request

[morrisonlevi]

/merge -c

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-07 03:58:24 UTC ℹ️ Start processing command /merge -c

[datadog-datadog-us1-prod]

More details

The refactor preserves the established uppercase remote-config product tokens for display and path parsing, including ASM_DD, LIVE_DEBUGGING, and LIVE_DEBUGGING_SYMBOL_DB, and all in-repository enum call sites were migrated. Focused Rust execution could not complete because the sandbox cannot fetch the workspace's pinned proptest git dependency.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 08be668 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}