---
title: "Why it's safe to experiment | Grafana Labs"
description: "Understanding Fleet Management's safeguards"
---

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

## Safeguards

Changing configuration across a fleet can feel risky. Nobody wants to push a bad config, stop data collection, or make an incident worse. Fleet Management is designed with safety in mind, with four safeguards that make it safe to experiment.

[Experiment with confidence](fleet-management-safeguards.svg "Experiment with confidence")

## Four safeguards

| Safeguard            | What it means                                          | Why it matters                              |
|----------------------|--------------------------------------------------------|---------------------------------------------|
| **Isolation**        | Local and remote Alloy configs run independently       | Remote errors don’t break local collection. |
| **Fallback**         | Invalid Alloy configs aren’t applied                   | Bad syntax doesn’t stop your collector.     |
| **Instant rollback** | Deactivate pipelines with one click                    | Recovery from any problem is fast.          |
| **Staged rollout**   | Use matchers to limit how many collectors are affected | Test on one collector before fleet-wide.    |

## What happens when things go wrong

| Scenario                      | What Alloy does                                   | Your action                            |
|-------------------------------|---------------------------------------------------|----------------------------------------|
| **Syntax error in pipeline**  | Rejects config, keeps last known good             | Fix syntax, re-save pipeline.          |
| **Pipeline causes high load** | Runs but collector health dashboards show warning | Deactivate pipeline, investigate.      |
| **Wrong collectors matched**  | Pipeline runs on unintended collectors            | Update matchers, deactivate if needed. |

> Isolation and automatic fallback are Grafana Alloy behaviors. The OpenTelemetry Collector merges local and remote configuration and doesn’t automatically roll back, so validate changes carefully when using it.