---
title: "How Fleet Management works | Grafana Labs"
description: "Architecture and data flow overview"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## How it works

Collectors register with Fleet Management, receive remote configurations, and send health telemetry back to Grafana Cloud.

[Fleet Management architecture showing collectors registering with Fleet Management, receiving remote configurations, and sending health telemetry to Grafana Cloud](fleet-management-architecture.svg "Fleet Management architecture showing collectors registering with Fleet Management, receiving remote configurations, and sending health telemetry to Grafana Cloud")

## The flow

1. **Register**: The collector registers itself with Fleet Management, declaring its identity, its attributes, and that it’s ready to receive remote configuration.
2. **Discover**: Each collector appears in the Fleet Management inventory, where you can see its health status, version, operating system, and the attributes you’ve assigned, such as `env`, `region`, or `team`.
3. **Configure**: You create configuration pipelines and assign them to collectors with attribute matching, for example, every collector where `env=production`.
4. **Distribute**: Collectors poll the Fleet Management API for matching configurations.
5. **Monitor**: Collector health telemetry flows back to Fleet Management dashboards.

## Key concepts

| Concept                    | What it means                                                 |
|----------------------------|---------------------------------------------------------------|
| **Collector**              | A telemetry collector registered with Fleet Management        |
| **Configuration pipeline** | A piece of config that can be assigned remotely               |
| **Attribute**              | Key-value pair used to match pipelines to collectors          |
| **remotecfg block**        | Local config that registers a collector with Fleet Management |

## Local + remote configs

**Grafana Alloy** runs local and remote configurations **in parallel**, isolated from each other. This means:

- Remote config errors don’t break local config.
- You can mix and match based on your needs.
- Gradual migration from local to remote is safe.

> The OpenTelemetry Collector works differently. Its Supervisor merges local and remote configuration and doesn’t automatically roll back to the last working remote config, so validate remote changes carefully when using it.