---
title: "Create a custom Alloy configuration pipeline | Grafana Cloud documentation"
description: "Learn how to create a custom Grafana Alloy configuration pipeline in Grafana Fleet Management"
---

# Create a custom Alloy configuration pipeline

With [configuration pipelines](/docs/grafana-cloud/send-data/fleet-management/introduction/glossary/#configuration-pipeline), you can control collector behavior remotely and at scale. Configuration pipelines are made up of a unique name, a content body, and matching attributes.

This page explains how to build a custom Alloy configuration pipeline in the Grafana Fleet Management interface using the Alloy component editor. The editor provides a catalog of approximately 180 [components](/docs/grafana-cloud/send-data/alloy/reference/components/) across 12 categories, including Prometheus, Loki, OpenTelemetry, and others. Fill in a form to set up each component instead of writing Alloy syntax by hand.

You can also create pipelines from a template or write them yourself:

- Refer to the [integration template setup guide](/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/integrations/) to use a pre-built pipeline.
- Refer to the [Alloy reference documentation](/docs/grafana-cloud/send-data/alloy/reference/) to help you write a pipeline.

## Before you begin

To create configuration pipelines in Fleet Management, you should:

- Have a Grafana Cloud account.
- Have administrator privileges or the ability to create and edit configuration pipelines. Refer to [Roles and permissions in Fleet Management](/docs/grafana-cloud/send-data/fleet-management/set-up/role-based-access-control/) for more information.
- Update Grafana Alloy to the most [current version](https://hub.docker.com/r/grafana/alloy). **The Alloy component editor must be used with Alloy v1.15.1 or later.**
- Understand the [key terms and concepts](/docs/grafana-cloud/send-data/fleet-management/introduction/glossary/) of Fleet Management and [how the service works](/docs/grafana-cloud/send-data/fleet-management/introduction/architecture/).

## Define the configuration pipeline

Build a pipeline by adding and linking Alloy components in the component editor.

01. In your Grafana Cloud stack, click **Connections** > **Fleet Management** and then switch to the **Remote configuration** tab.
02. Click **Create configuration pipeline**.
03. Click **Custom configuration** and then **Next**.
04. Enter a unique name for the pipeline.
05. Click **Add Component** to open the component catalog. A drawer opens with a searchable catalog of Alloy components grouped by category.
06. Type in the search field to find a component by name
07. Click the [component](/docs/grafana-cloud/send-data/alloy/reference/components/) you want to add. The drawer displays a form with the component’s required arguments, optional arguments, and fields for referencing other components.
08. Fill in the fields.
09. To reference another component, for example in the `forward_to` or `receiver` arguments, select the dropdown arrow in the reference box. The menu lists the compatible components already defined in the pipeline. If the component you want to reference isn’t in the list, add it to the pipeline first, then edit the referencing component.
    
    [](/media/docs/fleet-management/screenshot-fleet-management-component-editor-reference-dropdown.png)
10. When the form is complete, click **Save**. The editor appends the new component block to the end of your configuration.
11. Continue adding components until the pipeline is complete. Each pipeline must be self contained and have the necessary components to send telemetry over the network to persistent storage.
    
    > Note
    > 
    > Components can be reused across pipelines with an advanced Fleet Management feature called [pipeline export injection](/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/pipeline-export-injection/).
12. If you want to label the telemetry you collect, [inject collector attributes](/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/pipeline-attribute-injection/) into the pipeline.
13. Scroll down to click **Test configuration pipeline** to validate the configuration. The pipeline editor runs two checks and provides real-time feedback for:
    
    - Syntax.
    - Configuration validity. The editor validates against several Alloy versions to see if the pipeline will load successfully. When a warning is reported, the Alloy version where the issue was found is listed along with the error. Compare that version to the Alloy version of your matched collectors to decide whether the warning is something you need to fix now or a notice for a future upgrade.
    
    The validation checks can pass with no issues, pass with warnings, or fail. Warnings don’t prevent you from creating the pipeline. Failures block you from saving the pipeline. If an issue is reported, you can make the fix yourself or click the **Assistant** button and select **Fix errors in Assistant**.
    
    > Note
    > 
    > If you don’t see the Grafana Assistant button or the button is disabled, Assistant has not been enabled on your stack. Contact your stack administrator for more details.
14. To understand how your pipeline works, the different components in use, and potential areas for optimization, click the **Assistant** button. You can choose to have [Grafana Assistant](/docs/grafana-cloud/machine-learning/assistant/) explain the pipeline, validate the syntax or fix errors if there are any, optimize the configuration, or create a diagram of the pipeline.
    
    [](/media/docs/fleet-management/screenshot-fleet-management-assistant-button-task-menu-custom-v3.png)
15. Click **Next** to assign the configuration pipeline to collectors or click **Save** to save an incomplete pipeline.

## Assign the configuration pipeline

Configuration pipelines are incomplete until you add matching attributes that assign them to collectors.

> Note
> 
> If you saved an incomplete configuration, click the Edit icon from the **Configuration pipeline list** to return to the **Define a configuration pipeline** page.

1. Click **Next** on the **Define a configuration pipeline** page.
2. Use the dropdown menus to create a [matching attribute](/docs/grafana-cloud/send-data/fleet-management/introduction/glossary/#attribute-matching). The **Collector list** updates in real time to show you which collectors have been assigned the configuration pipeline. Only active collectors are displayed in this list by default. [Inactive collectors](/docs/grafana-cloud/send-data/fleet-management/manage-fleet/collectors/collector-status/#inactive-collectors) are not shown, but you can include them by updating the status filter.
3. Continue adding matching attributes as needed. `GetConfig` polling requests to the API can accept a maximum of 25 attributes.
4. Click **Save** to activate the configuration pipeline and return to the **Configuration pipeline list**.
5. Activate or deactivate a configuration pipeline with a click of the **Active** switch.
6. To verify the pipeline details without re-entering the editor, click on the pipeline name. You see a details drawer containing pipeline metadata, configuration content, and matched collectors.
   
   Assigning the matching attribute `profiling_enabled=true`.

## Next steps

Now that you’ve started remotely configuring your fleet, learn how to [streamline your workflows](/docs/grafana-cloud/send-data/fleet-management/streamline-workflows/) and [track historical changes](/docs/grafana-cloud/send-data/fleet-management/manage-fleet/pipelines/view-pipeline-history/) to your configuration pipelines.