Repository navigation
chore(traces): move trace normalization primitives out of the OTLP module - #2705
ajgajg1134 wants to merge 1 commit into
Conversation
…dule Move common/otlp/traces/normalize.rs to common/traces/normalize.rs so the upcoming Datadog v1.0 trace ingest path can share it with the OTLP translator. Items previously scoped pub(super) become pub(crate). No behavior change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Binary Size Analysis (Agent Data Plane)Baseline: 60cea0c · Comparison: 9b5291d · 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 ( |
Summary
Moves
common/otlp/traces/normalize.rstocommon/traces/normalize.rs. This is the first of a stack of small PRs building the Datadog-native v1.0 (ETP) trace ingest pipeline. The v1.0 path will need the same span normalization rules as the OTLP translator, so they should live outside the OTLP module.Pure move: the only edits are the module declarations, the import path in
transform.rs, the file's doc comment, and wideningpub(super)items topub(crate). No behavior change.Change Type
How did you test this PR?
make check-all: cleancargo nextest run -p saluki-components -E 'test(/traces/)': 81/81 passed, including the moved normalization testsReferences
Part of #2438 (Datadog-native intake).
🤖 Generated with Claude Code