-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Add filterprocessor #7094
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add filterprocessor #7094
Conversation
Signed-off-by: Yuri Shkuro <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7094 +/- ##
=======================================
Coverage 96.10% 96.10%
=======================================
Files 358 358
Lines 21584 21585 +1
=======================================
+ Hits 20744 20745 +1
Misses 633 633
Partials 207 207
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: Yuri Shkuro <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
## Which problem is this PR solving? - When previous PR #7094 was force-merged with binary size check failing (there's no way to override that check to succeed), the same check [failed](https://github.com/jaegertracing/jaeger/actions/runs/14816241094/job/41597074760) on `main` AND the steps to update the binary size cache did not run ## Description of the changes - Change the check for size to not run when on the main branch ## Testing - The check is expected to still fail for this PR and will have to be force-merged - But then the same check on main should succeed and update the cached value Signed-off-by: Yuri Shkuro <[email protected]>
## Which problem is this PR solving? - Resolves jaegertracing#6930 ## Description of the changes - Import `filterprocessor` as a counterpart to `attributeprocessor` - Increases the binary size by 2.18%, more than our "accidental" threshold, but acceptable ``` Previous binary size: 100223599 bytes New binary size: 102409625 bytes ❌ binary size increased by more than 2% (2.18%) ``` --------- Signed-off-by: Yuri Shkuro <[email protected]>
## Which problem is this PR solving? - When previous PR jaegertracing#7094 was force-merged with binary size check failing (there's no way to override that check to succeed), the same check [failed](https://github.com/jaegertracing/jaeger/actions/runs/14816241094/job/41597074760) on `main` AND the steps to update the binary size cache did not run ## Description of the changes - Change the check for size to not run when on the main branch ## Testing - The check is expected to still fail for this PR and will have to be force-merged - But then the same check on main should succeed and update the cached value Signed-off-by: Yuri Shkuro <[email protected]>
## Which problem is this PR solving? - Resolves jaegertracing#6930 ## Description of the changes - Import `filterprocessor` as a counterpart to `attributeprocessor` - Increases the binary size by 2.18%, more than our "accidental" threshold, but acceptable ``` Previous binary size: 100223599 bytes New binary size: 102409625 bytes ❌ binary size increased by more than 2% (2.18%) ``` --------- Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: amol-verma-allen <[email protected]>
## Which problem is this PR solving? - When previous PR jaegertracing#7094 was force-merged with binary size check failing (there's no way to override that check to succeed), the same check [failed](https://github.com/jaegertracing/jaeger/actions/runs/14816241094/job/41597074760) on `main` AND the steps to update the binary size cache did not run ## Description of the changes - Change the check for size to not run when on the main branch ## Testing - The check is expected to still fail for this PR and will have to be force-merged - But then the same check on main should succeed and update the cached value Signed-off-by: Yuri Shkuro <[email protected]> Signed-off-by: amol-verma-allen <[email protected]>
Which problem is this PR solving?
Description of the changes
filterprocessor
as a counterpart toattributeprocessor