-
Notifications
You must be signed in to change notification settings - Fork 438
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
Log a warning when the BatchSpanProcessor queue is full. #1871
Log a warning when the BatchSpanProcessor queue is full. #1871
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1871 +/- ##
==========================================
- Coverage 85.77% 85.71% -0.05%
==========================================
Files 171 171
Lines 5240 5241 +1
==========================================
- Hits 4494 4492 -2
- Misses 746 749 +3
|
Thanks @johanpel for the PR. FYI, there is a delay in running CI, because we have to manually allow it after a new commit, due to github rules for first time contributors. I see the CLA is signed already, which is great. Once this PR is merged, the process will be much easier ;-) |
Makes sense. I've added a few commits to hopefully fix the CI issues. Most were related to the timing around the I've reduced the queue size. Hope that gives more consistent results. |
It was still a bit too flaky, added a commit to only check logs if anything is actually dropped. |
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.
LGTM
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.
LGTM, thanks for the fix.
Fixes #1870
Changes
Adds a warning when a span is dropped in case the
BatchSpanProcessor
queue is full.CHANGELOG.md
updated for non-trivial changes