Hello! A colleague just pointed me to your project, looks awesome! There is definitely a need for this in our industry.
I have been working on something similar, but rather than have multiple projects doing similar things, I am looking at maybe jumping on your bandwagon. OpenTelemetry is focused on visualizing and improving the flow of requests and messages through a software system. But the same goals exist for a devops system, except in this case the work flowing through are not requests and messages but features and stories. So what I have been looking at is taking advantage of the industry support, APIs and tooling around OpenTelemetry and leveraging it for devops process visibility and tuning. Looking at your system, you have an excellent framework for connecting to various data sources, collecting data, storing the data and then building dashboards around it. I was imagining we could find a way to plug that data into OpenTelemetry through an OpenTelemetry collector. Then you can pick and choose from the many OpenTelemetry vendors to help you query, visualize and build dashboards around what I call "Flow Telemetry". I would love your thoughts. Have you looked at this and decided it wasn't a good match. Do you have concerns or questions? Thoughts on how to best create an integration? I was imagining either creating a new data store implementation that pushes data to an OTel Collector, but I am not sure how tied to SQL your current implementation is. Thanks, David https://www.linkedin.com/in/davidvc/ (also a member of the Apache DB PMC although I haven't been active for like 20 years :) ).
