Hi team followed quarkus opentelemetry guidelines ...
# support
j
Hi team followed quarkus opentelemetry guidelines but still not able to get proper logs in signoz. the trace id and span id is being printed in quarkus container logs but in signoz it is not getting captured as part of default fields
v
@nitya-signoz
n
We haven’t tested out quarkus yet. Can you give us some more idea about the setup?
d
Hi, We're trying to use signoz with quarkus opentelemetry too and struggling. We've followed the instructions to install signoz using docker-compose and have validated we can log into the frontend. We've adjusted the default grpc port to use 8080 while we're playing around and have proven the tcp port is listening on the server. Finally we follow https://quarkus.io/version/2.13/guides/opentelemetry and this is where things fall apart, we increased logger level when running our quarkus app and here's the output: 14:49:04 INFO traceId=d83b718db7e961b692d284d410ca980f, parentId=, spanId=3559247056d434bd, sampled=true [or.ac.op.TracedResource] (executor-thread-0) hello 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp http://mydomain.local:8080/...) >> CONNECTION 505249202a20485454502f322e300d0a0d0a534d0d0a0d0a 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp http://mydomain.local:8080/...) >> 0x00000000 6 SETTINGS 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp http://mydomain.local:8080/...) >> 0x00000000 4 WINDOW_UPDATE 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp http://mydomain.local:8080/...) >> 0x00000003 113 HEADERS END_HEADERS 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp http://mydomain.local:8080/...) >> 0x00000003 615 DATA END_STREAM 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp mydomain.local) << 0x00000000 24 SETTINGS 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp mydomain.local) << 0x00000000 4 WINDOW_UPDATE 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp mydomain.local ACK Settings) >> 0x00000000 0 SETTINGS ACK 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp mydomain.local) << 0x00000003 4 RST_STREAM 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp mydomain.local) << 0x00000000 0 SETTINGS ACK 14:49:08 SEVERE traceId=, parentId=, spanId=, sampled= [io.op.ex.in.gr.OkHttpGrpcExporter] (OkHttp http://mydomain.local:8080/...) Failed to export spans. The request could not be executed. Full error message: stream was reset: NO_ERROR 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [ok.in.ht.Http2] (OkHttp mydomain.local) >> 0x00000000 8 GOAWAY 14:49:08 FINE traceId=, parentId=, spanId=, sampled= [io.op.sd.tr.ex.BatchSpanProcessor] (BatchSpanProcessor_WorkerThread-1) Exporter failed Do you have any ideas why this is happening? We tried using the cloud hosted version too and the exact same issue occurs. Thanks
Just a heads up, after some digging, it appears this is the result of a firewall protecting us from HTTP2, we've got things working now and I have to say that troubleshooting tool of yours did the trick to help us understand our issues.