{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/233625875eec46508c26ae315cd52d19\" frameborder=\"0\" width=\"2560\" height=\"1920\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1920,"width":2560,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1920,"thumbnail_width":2560,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/233625875eec46508c26ae315cd52d19-45ca0ec1b7b5e9e7.gif","duration":266.0267,"title":"[Demo] Add telemetry for vital fleetd errors - Issue #23413","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."}