---
title: "Use a Grafana Cloud integration to create a configuration pipeline | Grafana Cloud documentation"
description: "Learn how to use Grafana Cloud integrations to create configuration pipelines in Grafana Fleet Management"
---

# Use a Grafana Cloud integration template to create a configuration pipeline

Grafana Fleet Management supports several Grafana Cloud integrations. You can generate pre-configured templates from these integrations and use the templates to configure your fleet remotely and at scale.

## Before you begin

To use integrations to create configuration pipelines in Fleet Management, you should:

- Have a Grafana Cloud account.
- Have administrator privileges and the ability to create and edit access policies.
- Update Grafana Alloy to the most [current version](https://hub.docker.com/r/grafana/alloy). Fleet Management must be used with Alloy collectors and is recommended for use with Alloy v1.7.2 or later. If you’re using an earlier version, make sure to include the `--stability.level=public-preview` flag when running Alloy.
- 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/).
- Make sure that you’ve completed the **Before you begin** requirements for the integration you’re using. You can find these prerequisites in [Integrations reference](/docs/grafana-cloud/monitor-infrastructure/integrations/integration-reference/).

## Select an integration template

1. In your Grafana Cloud stack, click **Connections** > **Fleet Management** and then switch to the **Remote configuration** tab.
2. Click **Create configuration pipeline**.
3. Select the platform of the host where Alloy is running.
4. Search or browse for an integration.
5. Select the integration you want to add and click **Next**. The Fleet Management application prefills a name for the configuration pipeline by combining the name of the integration and the platform.
6. Review the content of the new configuration pipeline and make any changes you might require.
   
   - You must replace any variables used in the pipeline with your own details. These variables are usually enclosed in angle brackets, for example `<your-cluster-name>` or `<your-instance-name>`.
   - Make sure that any environment variables used in the pipeline are set wherever Alloy is running, for example `GCLOUD_RW_API_KEY`.
   - [Inject collector attributes](/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/pipeline-attribute-injection/) to label the telemetry.
   - The Fleet Management application automatically appends a `remote_write` component to the integration configuration, so you do not need to add one to complete the pipeline.
   
   > Note
   > 
   > Configuration components, including `remote-write`, can be reused across pipelines with an advanced Fleet Management feature: [pipeline export injection](/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/pipeline-export-injection/).
7. 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.
8. 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-integration-v2.png)
9. 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 attributes `os=linux` and `env=DEV`.

## 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.