---
title: "Check the health status of a collector | Grafana Labs"
description: "Learn how to determine which of your collectors are unhealthy and need attention"
---

# Check the health status of a collector

If you’ve discovered a degraded collector in your fleet, Grafana Fleet Management can help you diagnose the problem. Watch video ->

Grafana Fleet Management provides a health status indicator so you can see at a glance if your collectors are healthy. You can find a collector’s health status in the **Status** column on the **Inventory** tab in the Fleet Management interface.

The health status indicator reflects the current state of the collector:

- [Green](#green-status) (Healthy) means the collector is healthy.
- [Yellow](#yellow-status) (Warning) means the collector is potentially unhealthy.
- [Red](#red-status) (Error) means the collector is unhealthy.
- [Gray](#gray-status) (Unknown) means the collector is not reporting data.

You can filter your fleet by status by clicking on the **Status** dropdown on the **Inventory** tab.

## How health status is determined

The health status is controlled by the following factors:

- Has the collector made a `GetConfig` API request in the last 30 minutes?
- Does the collector have any active alerts?
- Is the collector reporting any remote config status errors?

> Note
> 
> Remote config status reporting requires Alloy v1.12 or later.

The Fleet Management service fetches active alerts from the Grafana Prometheus instance. You must create alerts in your stack’s Prometheus Alertmanager to make them discoverable by the health status check. Refer to [Create new alerts](/docs/grafana-cloud/send-data/fleet-management/manage-fleet/collectors/troubleshoot-unhealthy-collector/alerts/#create-new-alerts) for guidance on labeling alerts and the [Alertmanager documentation](/docs/mimir/latest/manage/tools/mimirtool/#alertmanager) for tips on using Mimirtool to configure Alertmanager.

The Inventory status indicator reflects the collector’s overall health. Remote configuration status is reported more fully in the collector details view, which shows a separate configuration rollout status indicator beside the collector ID. Refer to [Troubleshoot remote configuration errors](/docs/grafana-cloud/send-data/fleet-management/manage-fleet/collectors/troubleshoot-unhealthy-collector/remote-configuration-errors/#troubleshoot-configuration-rollout-issues) if the rollout experiences errors.

### Green status

A green health status indicates that the collector is operational. At minimum, an operational collector:

- Has no active alerts.
- Made a `GetConfig` API request in the last 30 minutes.
- Has no remote config status errors.

> Note
> 
> A false-positive healthy status can result if the `collector_id` label in an alert does not match the `id` argument in the `remotecfg` block of the collector. If the labels do not match, the alerts cannot be attributed to the collector. When Fleet Management checks the state of a mismatched collector, the service finds no active alerts.

### Yellow status

A yellow health status warns that there might be an issue with the collector. It can have several causes:

- **Warning**: The collector is in one of the following states:
  
  - It has an active, non-critical alert.
  - It has not made a `GetConfig` request in the last 30 minutes.
  - Both of the above conditions are true.
- **Warning (Inactive)**: The collector is inactive. A collector becomes inactive in one of two ways:
  
  - It was gracefully shutdown, which immediately marks it as inactive regardless of its last `GetConfig` request time. This behavior was introduced in Grafana Alloy v1.13.0.
  - It has not made a `GetConfig` request in the last 3 hours.
  
  The inactive collector might or might not also have an active, non-critical alert.

### Red status

A red health status indicates one or more of the following:

- The collector has an active, critical alert.
- The collector has a configuration pipeline status error reported by the latest remote configuration. You can view detailed error information, including line and column numbers of the faulty pipeline, in the **Configuration** tab of the collector’s details view. Refer to [Troubleshoot remote configuration errors](/docs/grafana-cloud/send-data/fleet-management/manage-fleet/collectors/troubleshoot-unhealthy-collector/remote-configuration-errors/) for more information.

### Gray status

A gray health status indicates that the collector has not reported telemetry. It has never had a heartbeat and has no active alerts.

In the next milestone, you’ll learn how to interpret dashboards that show a collector’s internal metrics.