Update the configuration

Rolling out a change follows the same loop as building: edit, test, publish. You then assign the new version to the fleet's deploy group, and collectors in the group apply it on their next check-in.

This page covers server fleets. A Kubernetes bridge fleet assigns configuration versions per collector, singly or in bulk. See Kubernetes fleets.

Roll out a new version

1. Edit the configuration in the editor and test it.
2. Publish the new version.
3. On the fleet's Deploy Groups tab, select Edit on the deploy group, choose the new published version, and select Save.
4. Track the fleet's detail page. Collectors in the group move from Pending pickup to Applying to In sync as they receive and apply the version.

Collectors pull from Telflo, so you do not change anything on the hosts. The rollout happens remotely.

A fleet can have several deploy groups, each with its own assigned version, so a rollout applies to one group at a time. See Create a fleet.

Try a version on one collector first

To test a new version on a single collector before changing the group, pin the collector to it.

1. On the Collectors tab, select Edit collector in the collector's Actions column. The Edit collector dialog opens.
2. Under Configuration and Version, select the configuration and version to pin. The pin can target any published configuration; the group's assignment is marked group default.
3. Select OK. The collector is marked Pending pickup until its next check-in.

A pinned collector runs its pinned version and ignores changes to the group's assigned version. To return it to the group, open the dialog again and pick the option marked group default, which clears the pin.

Roll back

To roll back, edit the deploy group again and assign an earlier published version. Instances converge on it the same way and report In sync once applied. Version names make it easier to choose the rollback target. See Versions & publishing.

If an apply fails

An instance that reports Apply failed rejected the configuration.

1. Open the configuration, then validate and test it.
2. Check the collector's logs on the host for the reason.
3. Publish a corrected version and assign it to the deploy group.