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
Fix OpenTelemetry late bound span processors #18686
Conversation
- Fixes quarkusio#18575 - Changes default in `LateBoundBatchSpanProcessor` for `isEndRequired()` to `true`. In multiple span processor situation, this is necessary to ensure spans are reported
@hacst could you verify this fixes it for you? I've verified locally and I think it's good, but would be great to have additional verification |
is there any way to add this to automated tests? |
It would require an example with multiple exporters present, so likely a whole other module |
Thanks a lot for the fix. I'll have to look into how to build a custom quarkus version to test this (or are there Nightly builds in some repository I am unaware of?). Will try to do so tomorrow. |
@hacst not sure if there are nightlies or not. The easiest way is to check out either the PR, or my branch with the fix, and then run |
I verified that a Quarkus with this fix resolves the issue in my testing. Thanks a lot. |
@kenfinnigan while the issue is gone (export works) I still see the warning in the log on startup (tried only with dev server):
Is that expected? |
@hacst Likely yes, as all it means is the first time the late bound is accessed the delegate isn't present, probably during instantiation of the It might be possible to tweak things in the multi processor situation to not output the message, but it would require investigation and may not be possible |
LateBoundBatchSpanProcessor
forisEndRequired()
totrue
. In multiple span processor situation, this is necessary to ensure spans are reported