---
title: "Why use a staged rollout strategy? | Grafana Labs"
description: "Why use a staged rollout strategy? Rolling out a new pipeline to your entire collector fleet at once is risky. A misconfigured pipeline can silently drop telemetry or break collectors in production before you can react."
---

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

# Why use a staged rollout strategy?

Rolling out a new pipeline to your entire collector fleet at once is risky. A misconfigured pipeline can silently drop telemetry or break collectors in production before you can react.

Fleet Management gives you precise control over which collectors receive a configuration pipeline, using collector attributes as targeting filters. By tagging your collectors with an `env` attribute — such as `dev`, `staging`, or `prod` — and using regular expression matching in the pipeline assignment, you can expand a rollout incrementally across environments.

## Benefits of a staged rollout

A staged rollout strategy lets you:

- **Catch problems early** — Validate a pipeline in dev before it reaches production.
- **Control blast radius** — Limit the scope of any misconfiguration to a single environment.
- **Roll back instantly** — Deactivate a pipeline with a single click to stop delivery to all matched collectors.
- **Reuse one pipeline** — Expand the regex value rather than creating a new pipeline per environment.

In the next milestone, you’ll verify that your collectors have the `env` attribute set.