Documentation Grafana Cloud Instrument and send data Fleet Management Set up Configuration pipelines Remote configuration options

Remote configuration options

Remote configuration in Grafana Fleet Management can be a powerful tool for managing collectors at scale. Learn how to optimize Fleet Management for your unique observability setup.

Remote configuration only

If you want to configure your collectors fully remotely, you can move the contents of local configuration files to configuration pipelines in Fleet Management and add the remotecfg block to the empty local configuration files.

This method gives you maximum control over which configuration pipelines are in use. Turn pipelines off with a click of the switch. Combine them using matching attributes to build complete remote configurations based on each collector’s characteristics and your observability needs.

Hybrid configuration

If you want to continue configuring some parts of your collectors locally, add the remotecfg block to the end of each local configuration file. You can create supplemental configuration pipelines in Fleet Management that run in parallel with the local configuration.

Local configuration only

Although configuration pipelines are a central feature of Fleet Management, they are optional. You can choose to configure your collectors locally and use Fleet Management only to monitor their health and resource usage.

1. Add the remotecfg block to your local configurations to register your collectors with the Fleet Management service.
2. In your Grafana Cloud stack, click Connections > Collector > Fleet Management.
3. Confirm that your registered collectors appear in the Inventory tab.
4. Switch to the Remote configuration tab.
5. Disable the autogenerated self-monitoring configuration pipelines by turning the Active switch off.
6. To see health and status information in Fleet Management, make sure to add the collector_id label to your local configurations. Without this label, Fleet Management cannot correlate health data with a collector. You can add collector_id as an external label on all remote_write components, or you can create more targeted configuration pipelines to collect internal logs and metrics, adding the collector_id label only to those pipelines. The value of the collector_id label must match the id set in the remotecfg block.