---
title: "Alerts in Fleet Management | Grafana Cloud documentation"
description: "Use alerts in Grafana Fleet Management to troubleshoot your collectors."
---

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

# Alerts in Fleet Management

The Fleet Management service doesn’t come with out-of-the-box alerts, but it fetches user-created alerts managed by Grafana.

## View active alerts

You can view a collector’s active alerts in the Fleet Management interface:

1. In your Grafana Cloud stack, click **Connections** > **Fleet Management**.
2. Search, filter, or sort to find the alerting collector in your **Inventory**.
3. Click on the collector to open the details view drawer and switch to the **Alerts** tab.

> Note
> 
> If you don’t see active alerts in a collector’s details view, refer to [Alerts don’t appear in app](/docs/grafana-cloud/send-data/fleet-management/set-up/onboard-collectors/onboard-troubleshooting/#alerts-dont-appear-in-app) for guidance.

## Create new alerts

You can create alerts for collector health issues in [Grafana Alerting](/docs/grafana-cloud/observe-and-act/alert-and-measure-reliability/alerting/) in the Grafana Cloud UI.

> Note
> 
> Grafana-managed alerts have replaced datasource-managed alerts as the default and recommended way to use Grafana Alerting. Refer to the [Alerting documentation](/docs/grafana-cloud/observe-and-act/alert-and-measure-reliability/alerting/alerting-rules/) for details on this change. During this transition, the Fleet Management application displays both Grafana-managed and datasource-managed alerts. Users are encouraged to use Grafana-managed rules for new alerts and [migrate older datasource-managed alerts](/docs/grafana-cloud/observe-and-act/alert-and-measure-reliability/alerting/alerting-rules/alerting-migration/) for a unified experience.

For larger-scale workloads, refer to the [provisioning alerts documentation](/docs/grafana-cloud/observe-and-act/alert-and-measure-reliability/alerting/set-up/provision-alerting-resources/) to learn how to configure alerts programmatically. When setting up alerts, make sure the following labels are set so that the alerts are properly linked in Fleet Management:

- `collector_id`: The value of this label must match the collector’s unique ID in Fleet Management.
  
  - For Alloy collectors, `collector_id` should match the `id` argument in the collector’s `remotecfg` block.
  - For OpenTelemetry Collectors, `collector_id` should match the `service.instance.id` set by the OpAMP Supervisor. You can find this value in **Name/ID** column on the **Inventory** tab or in the `instance_id` field of the `persistent_state.yaml` file in the Supervisor’s storage directory.
- `severity`: The Fleet Management service uses the value of this label to assign a yellow or red health status indicator.
- `source="fleet-management"`: The value of the `source` label must be set to `"fleet-management"`.