---
title: "Determine if a collector is configured for Fleet Management | Grafana Labs"
description: "Learn how to know if your collector has already been registered with Fleet Management"
---

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

# Determine if a collector is configured for Fleet Management

In this milestone, you check whether your Grafana Alloy collector is already registered with Fleet Management.

Grafana Alloy is installed when you install a Grafana Cloud integration, Kubernetes Monitoring, Cloud Provider Observability, or Application Observability. Collector registration depends on the **Enable Remote Configuration** toggle during Alloy installation. By default, this toggle is enabled, so Alloy is registered as part of your fleet.

To determine if a collector is registered with Fleet Management, complete the following steps:

1. Open the **Inventory** tab.
2. Search, filter, or sort to find your collector in the **Inventory**.
3. Use **Status** to filter collectors by health status if needed.
4. Click the **Filter** button.
5. Use the dropdown menus to filter collectors by attributes if needed.

If your collector doesn’t appear on the list, you can manually add it. In the next milestone, you create the access token you need to manually add the collector to your Fleet Management inventory.

* * *

### More to explore (optional)

At this point in your journey, you can explore the following paths:

- [What is Grafana Alloy?](/oss/alloy-opentelemetry-collector)
- [Monitor multiple Linux hosts with the grafana\_agent role](/docs/grafana-cloud/developer-resources/infrastructure-as-code/ansible/ansible-multiple-agents/)
- [How Grafana Alloy Works: Demo (Video)](https://www.youtube.com/watch?v=NrnLyDXpfq0)
- [Grafana Alloy on GitHub](https://github.com/grafana/alloy)