The scaling challenge

Here’s the challenge that remote configuration solves. Imagine you need to add a new metrics scrape to your collectors—maybe you’re rolling out a new integration or collecting additional data for troubleshooting.

With the manual approach, you’d access each machine, edit the configuration file, reload the collector, and move on to the next one. For 5 collectors, that’s annoying. For 50 collectors, it’s a full day’s work. For 500 collectors, it’s impossible to do consistently without automation.

And even with automation tools like Ansible or Terraform, you’re still managing deployments, testing changes, and coordinating rollouts. Every configuration change becomes a project.

Remote configuration flips this model. Instead of pushing configs to each machine, you create a configuration pipeline once in Fleet Management. You assign it to collectors using attributes—maybe “all production collectors” or “all collectors in us-east.” The collectors pull the configuration automatically on their next poll cycle.

With remote configuration, one update reaches your entire fleet. That’s what makes Fleet Management a force multiplier.