---
title: "Configuration pipelines | Grafana Labs"
description: "Understanding how to create and manage remote configurations"
---

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

## Configuration pipelines

A configuration pipeline is the unit of remote configuration in Fleet Management. It’s configuration to perform one operation, such as monitoring MySQL. You can match multiple pipelines to a single collector and multiple collectors to a single pipeline.

Each pipeline has a name, configuration content, and matching attributes.

[Anatomy of a configuration pipeline](fleet-management-pipeline-anatomy.svg "Anatomy of a configuration pipeline")

## Key terms

| Term                       | What it means                                                                             |
|----------------------------|-------------------------------------------------------------------------------------------|
| **Remote configuration**   | All the configuration pipelines matched to a collector                                    |
| **Configuration pipeline** | The pieces of config you create and assign, usually representing one monitoring operation |

## Pipeline components

| Component               | Description                                  |
|-------------------------|----------------------------------------------|
| **Name**                | Unique identifier for the pipeline           |
| **Content**             | Standard configuration for one operation     |
| **Matching attributes** | Rules that assign the pipeline to collectors |

> **Pipelines are reusable.** Create once, assign to many collectors using attribute matching.