Our tracing information which we can see at console level is not the same when we see the logs in our backend UI which is Qryn #12268
Replies: 2 comments
-
I found the issue and solution. This was a small configuration issue in our otel config yaml file. We set the log format to raw and I did changed that to json and it worked fine now |
Beta Was this translation helpful? Give feedback.
0 replies
-
Solution was found |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We are using spring boot 2.7.1 version with two simple microservices Consumer and Producer. I have implemented the restTempalte and WebClinet communication with opentelemetry spring boot starter instrumentation. Also we had a logback.xml file for each project to have our custom logging pattern as well and we are using otel collector to export our logs from spring boot at port 4318
Now what we have see with the TCP dump when spring boot application is sending the logs to otel-collector most of the logs are not having the traceId and spanId which we can see in our console as mentioned. We need to export the logs how we see in our console the same to otel-collector.
Can someone point out where we are doing wrong.
Sample code can be found here : https://github.com/yatamraghu7/ManualInstrumentationOtel
Below are the screenshots:
This was for sure not an issue from our backend log viewer i.e. qryn because qryn uses clickhouse database and we logged into the database and verified that we are not even getting the trace information there as well. As mentioned when forwarding the logs from spring boot to otel-collector they are lost.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions