Managing configurations

Your configurations are on the Configurations screen, opened from the navigation. It lists the configurations in your current organization as cards, in a grid or list view.

Find a configuration

The list covers your own configurations and the ones published in your organization. telflo config list in the CLI returns the same set; another member's unpublished configuration is not visible to you in either place.

Search by name or description with the search box.
Filter the list with the dropdown: All configurations, Mine, or Published.
Each configuration shows a Published or Draft badge and a tag with its collector distribution, Otel Contrib or ClickStack. In list view, sort by Name, Owner, Distribution, Created, or Updated.

Work with configurations

Select New configuration to create one. The New configuration dialog offers Blank configuration for an empty canvas, or Start from a flow to begin from a prebuilt configuration. On the Name Your Configuration step, enter a Configuration Name and an optional Description. When more than one collector distribution is available to your account, the step also asks for the Distribution; for a flow, the step instead shows the flow's distribution and collector version as a read-only line ending in set by this flow. Otherwise the step has no distribution control: a blank configuration is created on OpenTelemetry Collector Contrib, and a flow's copy is created on the flow's distribution, or on OpenTelemetry Collector Contrib when the flow's distribution is not available to your account. See Flows.
Select Edit on a card to open a configuration in the editor.
Select the delete icon to remove a configuration you own.
Rename a configuration from the editor: hover its name in the toolbar and select the pencil icon, then press Enter to save or Escape to cancel.
From the terminal, telflo config create --name <name> -f <file> creates a configuration with the file as its draft version 1, stored without validation and locked to OpenTelemetry Collector Contrib; telflo config pull, push, and publish work on its versions afterwards. A configuration created this way appears in the list like any other. See Commands.

Each configuration has a name, an optional description, a collector distribution, the generated YAML, its pipelines, and its version history.

Collector distribution

Every configuration targets one collector distribution: OpenTelemetry Collector Contrib, the full upstream component catalog and the default, or ClickStack, ClickHouse's collector build with a smaller component set, available in private preview. The distribution is chosen when the configuration is created, on the Name Your Configuration step; when the step offers the Distribution choice, it states that the choice is locked once the configuration is created. It cannot be changed afterwards: to target a different distribution, create a new configuration and paste the YAML into its YAML view.

The collector distribution is chosen when a configuration is created and locked from then on. It decides which components the palette offers, which collector binary validates and tests the configuration, and which image the collectors run.

In the editor toolbar, the distribution appears next to Collector: as a read-only value with a lock icon, and the Version dropdown beside it lists that distribution's collector versions. A ClickStack configuration offers only the components ClickStack ships, validates and tests on the collector build its ClickStack version is based on, and deploys through a Kubernetes supervisor fleet or, on a server fleet, through the container image option, which runs Telflo's ClickStack collector image. See Kubernetes fleets. See Components and Kubernetes fleets.

Through the Telflo API and the CLI, only OpenTelemetry Collector Contrib is currently offered: telflo config create locks a new configuration to it, and a request that names any other distribution, including clickstack, is refused with Unknown collector distribution. A ClickStack configuration is created in the app, while ClickStack is available to your account. A configuration already locked to ClickStack keeps that distribution, and the API and CLI report it as stored; a test run of one of its stored versions that does not name a distribution runs on ClickStack.

Use Make Public & Share in the editor toolbar to create a read-only public-editor link for the current version. Telflo copies a /public-editor/<id> link to the clipboard. Anyone with the link can open the configuration in the public editor without an account, and sign in to save their own copy. The button's menu also has Edit Public Configurations for managing your existing public links.

A public link exposes the configuration's contents, including any values inserted from user variables; organization-variable references appear as unresolved $orgvar: tokens. Keep credentials out of the configuration by referencing environment variables with ${env:NAME} rather than storing them in the YAML.

The public editor has no saved configuration to lock, so its Collector control offers both a Distribution and a Version dropdown. A copy saved from the public editor after signing in is locked to the distribution chosen there.

Import an existing configuration

To manage an existing Collector config in Telflo, paste it into the YAML view of a new configuration. Telflo parses the YAML and builds the canvas from it. From the terminal, run telflo validate config.yaml and then telflo config create --name "<name>" -f config.yaml; the CLI stores the file as draft version 1 without validating it, so validate first. See Commands.

Next steps

Test a configuration before deploying it.
Publish and deploy it.