{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/4829a657ba5b46a7ab898d567611ab99\" frameborder=\"0\" width=\"2014\" height=\"1510\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1510,"width":2014,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1510,"thumbnail_width":2014,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/4829a657ba5b46a7ab898d567611ab99-00001.gif","duration":95.49999999999997,"title":"Understanding Trace Test Behavior on Jaeger","description":"In this video, I discuss a word behavior that we are experiencing with trace tests, specifically with traces from trace test tests in the under tools. I observed this behavior on both Jacker and Signals. I provide an example of the open telemetry of the checkout trace for the open telemetry demo, demonstrating that the operation works correctly without any issues. However, I encountered a problem when manually triggering the operation in the front. When attempting to check the trace test executed an hour ago, the algorithm throws an error indicating an unsupported value. Although this may be outside of our control, I suspect that there may be something in the trace span logging that is causing the problem. I will record another video showcasing a similar issue in Signals. It would be helpful if we could investigate this further."}