chore(config): migrate OTTL transform to typed configuration - #2263
chore(config): migrate OTTL transform to typed configuration#2263webern wants to merge 1 commit into
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Binary Size Analysis (Agent Data Plane)Baseline: 9e89350 · Comparison: dfe72f6 · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (5)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
055b852 to
1005c62
Compare
There was a problem hiding this comment.
More details
The migration consistently routes OTTL transform settings through the typed traces configuration, whose loader tests cover defaults, valid modes, invalid modes, unknown fields, file translation, and environment transport. No diff-only behavioral regression was found; focused Rust execution could not start because the sandbox could not fetch the pinned git dependency.
🤖 Datadog Autotest · Commit 0cb1e76 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
fedf507 to
dad25ce
Compare
d8f4844 to
ef23127
Compare

Summary
Migrate the OTTL span transform processor to the typed traces configuration. The processor now receives typed error-mode and transform-statement values, and its raw configuration adapter is removed.
Change Type
How did you test this PR?
make fmtmake check-docsmake check-clippymake check-allcargo check -p agent-data-plane --testsReferences