You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm following the example in https://quarkus.io/guides/opentelemetry to configure OpenTelemetry in my Quarkus service. The integration works fine and I can see the spans in Jaeger UI.
However, Quarkus logs don't include information on the tracing context, i.e.
09:53:37 INFO traceId=, parentId=, spanId=, sampled= [or.ac.HelloWorld] (executor-thread-0) Hello world executed.
Is there some configuration I might be missing? I've made a tiny project below if you want to see this in action.
Expected behavior
Logs populated with tracing context info.
Actual behavior
Logs not populated with tracing context info:
09:53:37 INFO traceId=, parentId=, spanId=, sampled= [or.ac.HelloWorld] (executor-thread-0) Hello world executed.
I upgraded to 2.11.0.CR1 and I can see them, I think it's this fix: #26258
Although in dev mode a live reload (i.e.. hit s) will cause OTEL to stop exporting and them to be traceId: '00000000000000000000000000000000' parentId: '' spanId: '0000000000000000' sampled: 'false'
and a rerun of tests (i.e. hit r) will cause OTEL to stop exporting and them to be traceId: '' parentId: '' spanId: '' sampled: ''
Need to fully restart quarkus dev to get them back.
Although in dev mode a live reload (i.e.. hit s) will cause OTEL to stop exporting and them to be traceId: '00000000000000000000000000000000' parentId: '' spanId: '0000000000000000' sampled: 'false' and a rerun of tests (i.e. hit r) will cause OTEL to stop exporting and them to be traceId: '' parentId: '' spanId: '' sampled: ''
Need to fully restart quarkus dev to get them back.
FWIW, I have created #29645 for that specific problem.
Describe the bug
I'm following the example in https://quarkus.io/guides/opentelemetry to configure OpenTelemetry in my Quarkus service. The integration works fine and I can see the spans in Jaeger UI.
However, Quarkus logs don't include information on the tracing context, i.e.
Is there some configuration I might be missing? I've made a tiny project below if you want to see this in action.
Expected behavior
Logs populated with tracing context info.
Actual behavior
Logs not populated with tracing context info:
How to Reproduce?
See the project in:
https://github.com/NMichas/quarkus-opentelemetry
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: