Overview
Deploy configurations to a fleet of collectors and manage them remotely.
Fleet management connects a configuration you built in Telflo to the collectors running in your infrastructure. Instead of copying YAML to each host, your collectors connect to Telflo, pull their configuration, and report their status.
You roll a configuration out to the fleet, watch each collector's health and status, detect drift from the version you approved, and roll back, all without logging into individual hosts.
Fleet management delivers configuration to your collectors and reads their status back. It is never in your telemetry data path: telemetry flows directly from your collectors to your backends.
The Fleet management section appears when fleet management is enabled for your account.
Fleets come in two types. In a server fleet, each collector connects to Telflo itself, from a host or a container. In a Kubernetes fleet, one bridge installed in the cluster connects to Telflo and manages the cluster's collectors. See Kubernetes fleets.
How it works
- Publish a configuration version. See Versions & publishing.
- Create a fleet from the published version. The fleet issues an install token and its deploy options. See Create a fleet.
- Install collectors from the fleet's deploy dialog: run the prebuilt collector image, or install a supervisor bundle on a host. See Install collectors.
- Each collector connects to Telflo, pulls its assigned configuration, applies it, and reports the result.
- Track the fleet from its detail page. See Monitor a fleet.
For a Kubernetes fleet, steps 2 and 3 differ: you create the fleet with a name only and deploy one bridge into the cluster. See Kubernetes fleets.
Key terms
| Term | Meaning |
|---|---|
| Fleet | A named group of collectors managed together, as a server fleet or a Kubernetes fleet. |
| Instance | A single collector that has enrolled in a fleet. |
| Bridge | The component a Kubernetes fleet installs in the cluster. It connects to Telflo and manages the cluster's collectors. |
| Install token | A credential embedded in a fleet's install options that authenticates its collectors to the fleet. |
| Default version | The published version a server fleet assigns to its instances. Set it with Set Default Version. Kubernetes fleets have no default version. |
| Served configuration | The configuration version Telflo has delivered to an instance. |
| Assigned configuration | The configuration version an instance is set to run. |
| Drift | An instance whose served configuration version does not match its assigned version. |
Prerequisites
- A configuration with a published version. See Versions & publishing.
- Hosts where you can run a collector, on Linux (arm64 or amd64/x86_64) as a container or directly on the host, or a Kubernetes cluster for a Kubernetes fleet.
Next steps
Last updated on