{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/c631bb6b0b304244a1ab1f2bd6895531\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/c631bb6b0b304244a1ab1f2bd6895531-e49bce59f1a15bea.gif","duration":334.835,"title":"End-to-End Proof of Concept for Traces Exporter Implementation 🚀","description":"In this video, I walk through the proof of concept (POC) I've been working on, focusing on the implementation of the TracesExporter that sends traces to the HotelCollector for processing. I've developed a custom plugin called HotelArrow that converts JSON schema into arrow format, which is then exported to our backend and stored in a database. I demonstrate the flow using a simple app that sends traces upon button clicks, and I show the resulting data in the database, including span and parent IDs. There are considerations regarding the scalability and development speed of our approach, and I invite viewers to think about whether we want a single collector or separate components for better flexibility. Please share your thoughts on this decision as we move forward."}