---
title: "When you might not need it | Grafana Labs"
description: "Situations where Fleet Management adds unnecessary complexity"
---

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

# When Fleet Management might not fit

| Signal                           | Why it might not be needed                        |
|----------------------------------|---------------------------------------------------|
| **1-5 collectors**               | Manual management is still manageable.            |
| **Static configurations**        | Configs rarely change after initial setup.        |
| **Distributed ownership**        | Each team owns and operates their own collectors. |
| **Identical configs everywhere** | All collectors run the exact same config.         |

## It’s OK to wait

Fleet Management scales down gracefully. You can:

- **Start simple**: Manage a few collectors manually.
- **Adopt later**: Add Fleet Management when the pain becomes real.
- **Try it out**: Register one collector to explore before committing.

## Still unsure?

Continue with this journey anyway. You can register a single collector to see how registration and health monitoring work firsthand, then decide whether managing a larger fleet this way is worth it.