Create a fleet

Create a fleet from a published configuration and get its install token.

A fleet is a named group of collectors managed together. There are two fleet types, chosen when you create the fleet:

  • A server fleet for collectors on hosts and in containers. Each collector connects to Telflo itself, and the fleet has a default configuration version.
  • A Kubernetes fleet for collectors in a Kubernetes cluster. One bridge connects to Telflo and manages the cluster's collectors. See Kubernetes fleets.

This page covers creating a server fleet. Creating one issues the install token and the deploy options your collectors need to connect.

Before you start

Have a configuration with a published version, unless you adopt collectors you already run with Import existing configuration. Only published versions can be deployed. See Versions & publishing.

Create a fleet

  1. Go to Fleet Mgmt and select New Fleet. The Create a new fleet dialog asks for the fleet type.
  2. Select Create New Supervisor Fleet. To create a Kubernetes fleet instead, select Create new Kubernetes Bridge Fleet; it asks only for a name. See Kubernetes fleets.
  3. Configuration. Select the published configuration to deploy. To adopt collectors you already run instead, select Import existing configuration: Telflo imports the YAML the first collector reports when it connects.
  4. Version. Select the published version. The most recent published version is selected by default.
  5. Name. Enter a name for the fleet. The name must be unique within your organization.
  6. Token expiry. Select how long the fleet's client token stays valid: Never, 180 days, 1 year, or 2 years.
  7. Select Create fleet.

The version you select becomes the fleet's default version, the version its instances run. Change it later with Set Default Version on the fleet's detail page. See Update the configuration.

After the fleet is created, the install files are available from the fleet's detail page. You can generate them again at any time.

Install token

Each fleet has an install token that authenticates its collectors. The token is embedded in the fleet's install options and identifies a collector as belonging to the fleet. It cannot be rotated or revoked; if it is exposed, re-create the fleet. The client token collectors use at runtime carries the expiry you chose and can be rotated and revoked from the fleet's Client Tokens tab. See Tokens & security.

Next steps

Install collectors from the fleet's deploy dialog. See Install collectors.

Last updated on

On this page