<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b599c15dc4da43a785a53e0b8354b080&quot; frameborder=&quot;0&quot; width=&quot;2014&quot; height=&quot;1510&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1510</height><width>2014</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1510</thumbnail_height><thumbnail_width>2014</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b599c15dc4da43a785a53e0b8354b080-00001.gif</thumbnail_url><duration>122.76666666666664</duration><title>Visualization Problem with Signoz 😊</title><description>Hi team! In this video, I want to show you another problem we&apos;re facing with signals. I&apos;ll walk you through an instance from a trace test using signals, where I encountered an error called &quot;missing spans.&quot; I&apos;ll demonstrate how this error is related to the API tests and discuss the possibility of a mistake in creating fake boot spans. We might need to check with lightstep, new relic, and other providers to see if there&apos;s an underlying issue. Let&apos;s dive in and investigate together!</description></oembed>