Telflo
Deployment

Overview

How Telflo deploys configurations to real collectors using fleets and OpAMP.

Deployment connects a configuration you built in Telflo to the collectors running in your infrastructure. Instead of copying YAML around by hand, your collectors connect back to Telflo and pull their configuration automatically, then report their status.

How it works

Telflo uses OpAMP (the Open Agent Management Protocol) to manage collectors remotely:

Published version  →  Fleet (issues token + install files)

            install on your hosts

        Collectors connect back via OpAMP  →  pull config, report status
  1. You publish a configuration version.
  2. You create a fleet from that published version. The fleet issues an install token and install files.
  3. You install collectors on your hosts using those files. Each collector runs a supervisor that speaks OpAMP.
  4. Collectors phone home to Telflo, pull their assigned configuration, apply it, and report back whether it applied successfully.
  5. You watch the fleet converge from the fleet dashboard.

Key terms

TermMeaning
FleetA named group of collectors that share a configuration. Created from a published version.
InstanceA single running collector that has connected to a fleet.
Install tokenA credential baked into the install files that authenticates a collector to its fleet. Can expire and be rotated/revoked.
Served configThe configuration version Telflo has delivered to an instance.
Assigned configThe configuration version an instance is supposed to run.
DriftWhen an instance's served config doesn't match its assigned config yet.

What you need first

  • A configuration with a published version (see Versions & publishing), or an existing collector config you want to adopt (see the import existing option in Create a fleet).
  • Hosts where you can install a collector.

Where to go next

On this page