Skip to content

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

Merged
merged 7 commits into from
May 4, 2025
Merged

Conversation

yurishkuro
Copy link
Member

@yurishkuro yurishkuro commented May 3, 2025

Which problem is this PR solving?

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]>
@yurishkuro yurishkuro requested a review from a team as a code owner May 3, 2025 15:18
@yurishkuro yurishkuro requested a review from joe-elliott May 3, 2025 15:18
@yurishkuro yurishkuro added the changelog:new-feature Change that should be called out as new feature in CHANGELOG label May 3, 2025
Copy link

codecov bot commented May 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.10%. Comparing base (e3c5d9f) to head (47a75aa).
Report is 1 commits behind head on main.

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           
Flag Coverage Δ
badger_v1 9.91% <ø> (ø)
badger_v2 2.05% <ø> (ø)
cassandra-4.x-v1-manual 14.91% <ø> (ø)
cassandra-4.x-v2-auto 2.04% <ø> (ø)
cassandra-4.x-v2-manual 2.04% <ø> (ø)
cassandra-5.x-v1-manual 14.91% <ø> (ø)
cassandra-5.x-v2-auto 2.04% <ø> (ø)
cassandra-5.x-v2-manual 2.04% <ø> (ø)
elasticsearch-6.x-v1 20.17% <ø> (ø)
elasticsearch-7.x-v1 20.25% <ø> (ø)
elasticsearch-8.x-v1 20.43% <ø> (ø)
elasticsearch-8.x-v2 2.05% <ø> (ø)
grpc_v1 11.46% <ø> (ø)
grpc_v2 2.05% <ø> (ø)
kafka-3.x-v1 10.19% <ø> (ø)
kafka-3.x-v2 2.05% <ø> (ø)
memory_v2 2.05% <ø> (ø)
opensearch-1.x-v1 20.30% <ø> (ø)
opensearch-2.x-v1 20.30% <ø> (ø)
opensearch-2.x-v2 2.05% <ø> (ø)
query 2.05% <ø> (ø)
tailsampling-processor 0.55% <ø> (ø)
unittests 94.91% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

yurishkuro added 6 commits May 3, 2025 11:46
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]>
Copy link
Contributor

@jkowall jkowall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@yurishkuro yurishkuro merged commit 673dbd1 into jaegertracing:main May 4, 2025
56 of 57 checks passed
@yurishkuro yurishkuro deleted the filterprocessor branch May 4, 2025 01:06
yurishkuro added a commit that referenced this pull request May 4, 2025
## 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]>
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
## 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]>
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
## 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]>
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
## 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]>
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
## 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:new-feature Change that should be called out as new feature in CHANGELOG
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: filterprocessor
2 participants