-
Notifications
You must be signed in to change notification settings - Fork 954
Add rate‑limited log warning when BatchSpanProcessor drops spans #8167
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
Open
VamshikrishnaMonagari
wants to merge
5
commits into
open-telemetry:main
Choose a base branch
from
VamshikrishnaMonagari:alert-through-logs-when-BatchSpanProcessor-drops-span
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+47
−0
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ff11a8b
Alert through logs for dropped spans in BatchSpanProcessor
VamshikrishnaMonagari 912e997
Fix variable name for throttling logger in BatchSpanProcessor
VamshikrishnaMonagari d14a2cc
Replace ThrottlingLogger with per-batch drop count logging in BatchSp…
VamshikrishnaMonagari ad025e3
Address test review feedback: use forceFlush and assert full message
VamshikrishnaMonagari 903425f
Fix checkstyle import ordering in BatchSpanProcessorTest
VamshikrishnaMonagari File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@jack-berg do you think it would make sense to add something to the SpanProcessorInstrumentation to get this information, rather than tracking it separately here?
/cc @anuraaga
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.
Would have to maintain state over there but at least it would be hidden behind a central abstraction
An otel maximalist answer here would be:
I'm not trying to boil the ocean for this though 😛
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.
Yeah if the
SpanProcessorInstrumentationwas already using an async counter or such with tracking, just reading that would be fine. But it's probably better to keep that synchronous (I think?) so keeping this BSP implementation detail in BSP seems to make more sense