---
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 you create in Fleet Management. When you configure a collector remotely, you’re creating at least one pipeline. Each pipeline holds standard collector configuration for a single operation, such as scraping MySQL metrics, built from components like `prometheus.scrape`, `loki.source.file`, or `prometheus.remote_write`.

You match a pipeline to collectors by their attributes. One pipeline can match many collectors, and one collector can match many pipelines. Each collector pulls the set of pipelines that match it, and that set is its **remote configuration**.

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")

## Pipeline components

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

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