Skip to content
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

Webflux + Kotlin lossing span #5154

Closed
xsmrcek opened this issue Jan 17, 2022 · 1 comment · Fixed by #5196
Closed

Webflux + Kotlin lossing span #5154

xsmrcek opened this issue Jan 17, 2022 · 1 comment · Fixed by #5196
Labels
bug Something isn't working repro provided

Comments

@xsmrcek
Copy link

xsmrcek commented Jan 17, 2022

Describe the bug
Instrumentation using agent is lossing span.
Every client request have new/different trecaparent.

Steps to reproduce
Build application from attachment, build docker image with app and nevest javaagent.
Configuration I use:
ENV OTEL_TRACES_EXPORTER="none"
ENV OTEL_METRICS_EXPORTER="none"
ENV OTEL_PROPAGATORS="tracecontext,b3,baggage"
I am testing just propagation now. ( I wan to use application insights javaagent in future/ As far as I know it is build on top of opentelemetry javaagent, so first I need this one working)
What did you expect to see?
Trace headers (traceparent, traceid, spanin etc is generated/propagated correctly)
What did you see instead?
New trace headers for every request.
What version are you using?
newest opentelemetry-javaagent (1.10.0)

Environment
openjdk 15 2020-09-15
spring-boot-starter-parent 2.5.5 (webflux)
kotlin 1.5.31
logbook (for logging) 2.4.1

@xsmrcek xsmrcek added the bug Something isn't working label Jan 17, 2022
@xsmrcek
Copy link
Author

xsmrcek commented Jan 17, 2022

I wan't able to upload an attachment, so I upload minimal exmaple here: https://github.com/xsmrcek/minimal-example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working repro provided
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants