Flows
Pre-built collector pipelines
A Flow is a collector pipeline that already works: the components, the order, the settings, and the reasoning behind them. Every one here is published in Telflo, where you adapt it, test it against real data, and push it to your fleet over OpAMP.
Replace vendor agents on your VM fleet
Scrapes CPU, memory, load, disk, filesystem, and network metrics plus system and application logs on every VM.
Ship OTel data to ClickHouse
The ClickStack (HyperDX) ingestion collector as upstream ships it: parses JSON log bodies into attributes, infers severity from level fields or the body text, and routes browser session-replay events to their own ClickHouse table.
Collect per-node telemetry with a DaemonSet
Per-node DaemonSet that scrapes kubelet and host metrics, tails pod logs with the container parser and file_storage checkpoints, enriches everything with k8sattributes, and forwards to the in-cluster gateway.
Running a setup you think should be a Flow? Tell us about it.
1
Open it in the editor
The flow arrives as a working pipeline on the canvas, every component configured and editable.
2
Adapt it, then test it
Change what's specific to you, then run the pipeline against recorded traffic and see exactly what comes out the other end.
3
Push it to the fleet
Roll it out over OpAMP, staged if you want, with one click back to the previous version if something looks wrong.
Start from a working pipeline
Free account, no card. Open a Flow, adapt it, and test it against sample data in a couple of minutes.