Configuration drift

Configuration drift is an instance whose served configuration version does not match the version currently assigned to it. You assigned a version, or rolled out a new one, but the instance is not running it yet.

Why drift happens

• The instance has not checked in since the assignment. It shows Pending pickup.
• The instance is mid-rollout. It shows Applying.
• The instance rejected the configuration. It shows Apply failed and stays on the previous version.
• The instance has gone quiet. It shows Stale and cannot be updated until it returns.

A healthy fleet trends toward zero drift, with every instance In sync with its assigned version.

See drift

The fleet detail page shows drift in two places: the per-instance status column, where any status other than In sync is drifting, and the stats strip, which shows a Version drift count for the fleet. See Monitor a fleet.

Resolve drift

• Pending pickup or Applying: usually resolves on its own as the collector checks in. Allow a heartbeat cycle.
• Apply failed: the configuration was rejected. Fix it and roll out again. See Update the configuration.
• Stale: the collector is unreachable. Check the host and the collector process. The instance catches up when it reconnects.