Flows
Start a configuration from a prebuilt, validated collector configuration.
A flow is a prebuilt OpenTelemetry Collector configuration from Telflo's curated catalog, each solving one problem, such as log volume cost control, tail sampling, PII redaction, or a Kubernetes telemetry stack. Using a flow creates your own configuration from it: an independent copy you edit like any other configuration.
Every flow is validated against a real collector binary of its pinned collector version, and contains no hardcoded destinations or credentials: endpoints and secrets are ${env:NAME} references you supply at deployment. The catalog is curated by Telflo; flows cannot be created or edited by users.
Browse flows
Open Flows from the navigation, or go to telflo.com/flows. The catalog is public, so you can browse it without an account.
- Search flows by name, summary, or tag, and filter by signal type: Traces, Metrics, or Logs.
- Each card shows the flow's name, a one-line summary, and the signal types it covers. Select View to open the flow.
A flow's detail page shows its full description, the complete collector YAML with the collector version it was validated against, and a Before you use this section listing what the configuration needs:
- Sends data to: the exporters in the configuration.
- The environment variables you must set before it runs.
Use a flow
Using a flow requires signing in; the catalog itself can be browsed without an account.
- Open the flow and select Use this flow.
- In the dialog, keep or edit the Configuration name and Description. They are prefilled from the flow.
- Select Create configuration.
Telflo creates a new configuration in your organization, with version 1 pinned to the flow's collector version, and opens it in the editor. The copy is independent: editing it does not affect the flow, and later updates to the flow do not change your configuration.
You can also start from a flow when creating a configuration: New Configuration opens a dialog with two options, Blank configuration and Start from a flow. See Managing configurations.
After you create the configuration
- Set values for the configuration's
${env:NAME}references in the deploy environment. They are also reported as deployment requirements by validation. - Adjust the pipeline, test it, then publish and deploy it like any configuration.
Last updated on