Helm charts, Argo CD ApplicationSets and OpenTofu that stand up and test a DFE deployment on Kubernetes.
The whole DFE stack on one host with Docker Compose, from pinned release images or local builds.
The template a DFE deployment's own git repo is seeded from.
Writes a DFE deployment's streams to compressed files in a local path or object store.
The DFE console, where an operator sets up and runs a deployment.
Loads Kafka and gRPC streams into ClickHouse in large batched inserts.
Runs a Vector pipeline as a supervised transform stage in a DFE deployment.
The DFE control plane: an API and CLI that turn operator changes into git commits a deployment runs from.
Defines the core ClickHouse objects and Kafka bootstrap topics a DFE deployment creates.
The front door of a DFE deployment: takes events in the protocols agents already speak and hands them on as JSON.
DFE fork of HyperDX extended with DFE 2.1 Discovery, JSON capabilities and dfe-ui integration. rerere for added functionality, security fixes post-applied.
Runs your VRL transforms over a DFE deployment's event stream, in-process.
Pulls data from cloud and SaaS APIs, databases and files into a DFE deployment.
Turns Beats and Elastic Agent events into DFE-normalised events.
To associate your repository with the data-fusion-engine topic, visit your repo's landing page and select "manage topics."