Flows

A flow is a prebuilt OpenTelemetry Collector configuration from Telflo's curated catalog, each solving one problem, such as PII redaction, host fleet monitoring, RED metrics from spans, or dual-shipping telemetry during a backend migration. 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, and each flow shows who built it; flows cannot be created or edited by users.

Browse flows

The catalog is available in two places: a public library on the website, and the Flows page in the app.

The public library

Go to telflo.com/flows. The library is public, so you can browse it without an account.

• Search flows by name or component, and filter by signal type and category, such as cost control, Kubernetes, or migration.
• A flow's page describes the problem it solves, how the data moves through its pipelines, each component's role, and the gotchas to know before running it.
• Use this flow in Telflo opens the flow in the app, where you sign in to continue.

Flows in the app

Open Flows from the navigation. Signing in is required.

• 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, who built it, and the signal types it covers. Select View to open the flow.

A flow's page in the app shows its full description and the complete collector YAML, with the collector version it was validated against. A Before you use this section lists what the configuration needs:

• Sends data to: the exporters in the configuration.
• The environment variables you must set before it runs.
• The organization variables to define in the vault. An organization variable the flow references but your organization has not defined is delivered to the collector as-is, not reported as an error.

A flow built from a published external configuration also links to its source.

Use a flow

1. In the app, open the flow and select Use this flow.
2. In the dialog, keep or edit the Configuration name and Description. They are prefilled from the flow.
3. 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.