Data observability that drives action. Detect and resolve data quality incidents faster by viewing data flowing through your systems and acting on them in real-time with Streamdal, the open-source data observability tool.
We're so excited to share the next evolution of Streamdal with PH! Thanks @mwseibel for Hunting us.
Streamdal is an open-source data observability tool that drives action. Data engineering teams will be able to detect and resolve data incidents faster by viewing data flowing through their systems and acting on it in real-time.
We built Streamdal because we've experienced a growing divide between the systems that handle data and the tooling used to detect and resolve incidents. Observing data happens downstream once data is already in data stores, while at the same time detecting and resolving data incidents typically requires you to trace the issue back upstream.
We believe both observability, detection, and resolution should exist upstream.
Streamdal helps teams overcome this divide by generating a real-time, dynamic visualization of the data flow: we call it “The Data Graph”. This means teams will get a dynamic bird's-eye view of their producers and consumers as they scale up and down in real-time. From there, they’ll be able to watch a live view of data flowing throughout their system.
By importing and wrapping a few lines of code with the Streamdal SDK, they’ll be able to detect data incidents the moment they happen. Along with the dynamic data graph, they’ll get throughput metrics, schema inference, and the ability to zoom in and observe real-time data - it's essentially a `tail -f`, but for data and in human readable format.
Today, we're excited to share our open-source product with the PH community! In this beta phase of our launch, we currently have SDK support for Golang, Python and Node.js. The UI and server components can be deployed in containers anywhere: on-prem or in cloud.
Coming very soon is a host of data quality management features allowing you to proactively interact with real-time data, and prevent downstream issues! Think of it as a `firewall` for your data.
We'd love to hear your thoughts, ideas, and feedback. We'll be here to answer questions in the comments.
