Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/create-custom-otel-pipeline.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/send-data/fleet-management/set-up/configuration-pipelines/create-custom-otel-pipeline/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Create a custom OpenTelemetry Collector configuration pipeline
With configuration pipelines, 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 create a custom pipeline for OpenTelemetry Collector in the Grafana Fleet Management interface. Type or paste an OpenTelemetry Collector YAML configuration in the configuration editor and then add matching attributes to assign it to specific collectors.
You can also create pipelines from a template. Refer to the integration template setup guide to use a pre-built 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 for more information.
- Have at least one OpenTelemetry Collector onboarded to Fleet Management using the OpAMP Supervisor.
- Understand the key terms and concepts of Fleet Management and how the service works.
Define the configuration pipeline
Write a complete OpenTelemetry Collector configuration in YAML and save it as a pipeline.
- In your Grafana Cloud stack, click Connections > Fleet Management and then switch to the Remote configuration tab.
- Click Create configuration pipeline.
- Select the OpenTelemetry collector type.
- Click Custom configuration and then Next.
- Enter a unique name for the pipeline.
- In the configuration editor, write your OpenTelemetry Collector YAML configuration. The configuration must be valid. Refer to OpenTelemetry Collector configuration for more details.
- Click Test configuration pipeline to verify the syntax is valid.
- Click Next to assign the configuration pipeline to collectors or click Save draft 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 pipeline, click the edit icon from the Configuration pipeline list to return to the Define a configuration pipeline page.
- Click Next on the Define a configuration pipeline page.
- Use the dropdown menus to create a matching attribute. 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 are not shown, but you can include them by updating the status filter.
- Continue adding matching attributes as needed. Configuration polling requests to the API can accept a maximum of 25 attributes.
- Click Save to activate the configuration pipeline and return to the Configuration pipeline list.
- Activate or deactivate a configuration pipeline with a click of the Active switch.
- To verify the pipeline details without re-entering the editor, click the pipeline name. You see a details drawer containing pipeline metadata, configuration content, and matched collectors.
Next steps
Now that you’ve started remotely configuring your fleet, learn how to streamline your workflows and track historical changes to your configuration pipelines.
Was this page helpful?
Related resources from Grafana Labs


