Key concepts
The terms used throughout Telflo and these docs.
This page defines the terms used throughout Telflo and these docs.
Configuration
A configuration is a named project: one canvas, one generated YAML document, and its version history. It is the unit you create, name, and open in the editor.
Version
A version is a snapshot of a configuration's canvas and YAML at a point in time, with an optional note. Telflo records a version each time you save.
- The current version is the one you are editing.
- Published versions and older versions are read-only. Editing a read-only version prompts you to save the changes as a new version.
Pipeline
A pipeline carries one signal type (traces, metrics, or logs) through a chain of receivers, processors, and exporters. A configuration can contain multiple pipelines, including custom-named pipelines such as traces/production. On the canvas, pipeline membership is defined by the edges you draw, and each pipeline is color-coded.
Collector version
Each configuration targets a specific OpenTelemetry Collector version, selected in the toolbar. The collector version determines which components and fields are valid, and which collector binary runs during a test.
Publishing
A saved version is private to the editor. Publishing marks a version as a release that can be deployed. Only published versions are available when you create or update a fleet. See Versions & publishing.
Fleet
A fleet is a named group of collectors that share one published configuration. You create and manage fleets in the Fleet management section. Creating a fleet issues an install token and a supervisor bundle. Collectors installed from that bundle connect to Telflo and pull their configuration. See Fleet management.
Instance
An instance is a single collector that has enrolled in a fleet. The fleet detail page lists each instance with its status and the configuration version it runs. Instance statuses are In sync, Pending pickup, Applying, Apply failed, and Stale.
Organization
Your work belongs to an organization. Members of an organization share its configurations and fleets. Each member has a role, Admin or Contributor, that controls what they can do. See Members & roles.
Vault
The vault stores reusable variables that you reference from a configuration with # and the variable's reference name, such as #PROD_API_URL. The vault is personal to your account. See Vault.