feat: use ip quantization when aggregating peer tags for trace stats#1944
Conversation
Clippy Allow Annotation ReportComparing clippy allow annotations between branches:
Summary by Rule
Annotation Counts by File
Annotation Stats by Crate
About This ReportThis report tracks Clippy allow annotations for specific rules, showing how they've changed in this PR. Decreasing the number of these annotations generally improves code quality. |
🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage (details) 🔗 Commit SHA: f2c6d5d | Docs | Datadog PR Page | Give us feedback! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1944 +/- ##
==========================================
- Coverage 71.99% 71.84% -0.15%
==========================================
Files 434 434
Lines 70450 70594 +144
==========================================
- Hits 50718 50717 -1
- Misses 19732 19877 +145
🚀 New features to boost your workflow:
|
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-unknown-linux-gnu
|
8692aa0 to
9fcf423
Compare
|
Being handled as part of #1819 |
|
My initial plan was to merge this change with my css obfuscation change to put it behind a feature flag but in the end we decided the change is small enough to not break anything (the agent's re-obfuscating peer tags should not change them) |
VianneyRuhlmann
left a comment
There was a problem hiding this comment.
LGTM, thanks for doing it
What does this PR do?
Quantize IP addresses for peer tags when aggregating trace stats.
Motivation
Needed for agent side stats computation in the Serverless Compatibility Layer (used as the agent in Azure Functions) in DataDog/serverless-components#124.
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.