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.
Survive backend outages with a persistent queue
Replaces the default in-memory exporter queue with a disk-backed queue that survives collector restarts, sized in items instead of opaque requests.
Fail over to S3 when ClickHouse backs up
A ClickHouse gateway that fails each signal over to an S3 overflow bucket when inserts back up and fails back on its own once ClickHouse recovers, so an ingest stall never becomes data loss.
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.