FAQ
Frequently asked questions about Telflo.
General
What is Telflo? A visual editor for OpenTelemetry Collector configurations. You build pipelines on a canvas, Telflo generates valid Collector YAML, and you can test and deploy the result to real collectors. See the Introduction.
Do I need an account? You can explore the editor in the public editor without one, but you need to sign in to save, test, publish, or deploy. See the Quickstart.
Can I import an existing Collector config? Yes. Paste it into the YAML view of a new configuration and Telflo rebuilds the canvas from it.
Pipelines
What components are available? Receivers, processors, exporters, and extensions — the available set depends on the collector version you target. See Components.
How are pipelines defined? By the edges you draw. Each edge belongs to one pipeline (traces, metrics, logs, or a custom name), and a node can be part of several pipelines. See Canvas & pipelines.
What's the difference between validation and testing? Validation checks the config is well-formed and schema-valid. Testing runs real sample telemetry through it on an actual collector. See Testing overview.
Versions & deployment
What's the difference between saving and publishing? Saving records a private version in the editor. Publishing marks a version as a release that can be deployed to a fleet. See Versions & publishing.
How do collectors get my configuration? They pull it from Telflo over OpAMP. You create a fleet, install collectors with its bundle, and they connect back and apply the assigned config. See Deployment overview.
How do I roll back? Assign an earlier published version to the fleet; instances converge on it. See Update the config.
AI assistant
Why don't I see the AI tab? AI must be enabled in Settings → AI, and access may need to be requested first. See AI access.
Will the AI change my configuration? In Build mode it can, applying edits to your canvas for you to review. Ask mode only answers questions. See Modes.
Security
Where do my secrets go? Use the Vault. Secrets are stored encrypted and exported as environment-variable references, so they never appear in your YAML, shared links, or version history.