Troubleshoot remote configuration errors
The Grafana Fleet Management application connects configuration pipeline errors to the collectors running the pipelines. On the Inventory tab, these collectors have a red health status that indicates an error has occurred and they are unhealthy. You might also see error logs reporting the collector’s failure to fetch the remote configuration.
Note
You must be running Grafana Alloy v1.12.0 or later to see remote configuration errors in the application interface.
For more information about a configuration error, go to the collector details view of an affected collector. When an error is present, you can see an expandable error panel that includes diagnostic details. Follow these steps to troubleshoot the configuration error without leaving the application.
In your Grafana Cloud instance, click Connections > Collector > Fleet Management.
On the Inventory tab, search, filter, or sort to find the affected collector.
Click on the collector ID to open the details view, which takes you directly to the Configuration tab.
If configuration errors are present, an error panel appears at the top of the tab.
Expand the Configuration Error(s) panel to see diagnostic details, including:
- Error messages describing what went wrong.
- Line and column numbers indicating where each error occurs in the remote configuration.
In the read-only remote configuration, find the line that corresponds to the error.
Scan backward in the configuration until you find the name of the erroring pipeline. Pipelines are named in a
declareblock. For example, the self-monitoring logs pipeline for Linux systems is named like this:declare "self_monitoring_logs_linux" {Once you know which pipeline caused the error and how to fix it, expand the Connected Pipelines section and click on the pipeline in the list. The link takes you straight to the pipeline editor, where you can make the necessary changes.



