Update the configuration

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

This page covers server fleets. A Kubernetes fleet has no default version; you assign 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, select Set Default Version and choose the published version.
4. Track the fleet's detail page. Instances 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.

Roll back

To roll back, set the fleet's default version to an earlier published version. Instances converge on it the same way and report In sync once applied. Version notes 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 set it as the fleet's default version.