-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[processor/tailsampling] Fixed sampling policy evaluation debug logging batch metrics #37040
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
[processor/tailsampling] Fixed sampling policy evaluation debug logging batch metrics #37040
Conversation
Signed-off-by: Sean Porter <[email protected]>
Signed-off-by: Sean Porter <[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.
I think this would deserve a new test, to avoid a regression, but I'm OK merging this as is, given that this is only used in a debug logging at the moment. Let me know what you prefer, @portertech.
Signed-off-by: Sean Porter <[email protected]>
@jpkrohling Thank you for the review! I added a test, is that what you had imagined? |
…ng batch metrics (open-telemetry#37040) #### Description Currently, the processor always logs (at debug) `sampled=0` and `notSampled=0` for every batch processed. This pull-request fixes those metrics. --------- Signed-off-by: Sean Porter <[email protected]>
…ng batch metrics (open-telemetry#37040) #### Description Currently, the processor always logs (at debug) `sampled=0` and `notSampled=0` for every batch processed. This pull-request fixes those metrics. --------- Signed-off-by: Sean Porter <[email protected]>
Description
Currently, the processor always logs (at debug)
sampled=0
andnotSampled=0
for every batch processed. This pull-request fixes those metrics.