<?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/233625875eec46508c26ae315cd52d19&quot; frameborder=&quot;0&quot; width=&quot;2560&quot; height=&quot;1920&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1920</height><width>2560</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1920</thumbnail_height><thumbnail_width>2560</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/233625875eec46508c26ae315cd52d19-45ca0ec1b7b5e9e7.gif</thumbnail_url><duration>266.0267</duration><title>[Demo] Add telemetry for vital fleetd errors - Issue #23413</title><description>In this video, I demonstrate how to simulate and troubleshoot a specific error in Fleet Desktop. By intentionally causing an error and restarting the FleetD agent, we aim to observe the error feedback sent back to Fleet. Additionally, I show how to extract error information from Redis and through the debug errors API. No action requested from viewers.</description></oembed>