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

Fleet Management is designed with safety in mind.

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

## Four safeguards

| Safeguard            | What it means                              | Why it matters                             |
|----------------------|--------------------------------------------|--------------------------------------------|
| **Isolation**        | Local and remote configs run independently | Remote errors don’t break local collection |
| **Fallback**         | Invalid configs aren’t applied             | Bad syntax doesn’t stop your collector     |
| **Instant rollback** | Deactivate pipelines with one click        | Fast recovery from any problem             |
| **Targeted testing** | Use matchers to limit blast radius         | 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 |