Troubleshoot configuration pipeline issues
Grafana Cloud

Note

Fleet Management is currently in public preview. Grafana Labs offers limited support, and breaking changes might occur prior to the feature being made generally available. For bug reports or questions, fill out our feedback form.

Troubleshoot configuration pipeline issues

This page describes how to troubleshoot issues you might have with your configuration pipelines.

Configuration pipeline was deleted from application

If you delete one of the autogenerated self-monitoring pipelines, you can recreate it by deleting the other pipelines named self_monitoring_*. Once the last autogenerated pipeline is deleted, the Fleet Management service recreates them all.

If you do not want to use the self-monitoring pipelines, switch them off in the Fleet Management interface rather than deleting them.

If you delete a user-created configuration pipeline, you need to recreate it. How you recreate it depends on how much time has passed since the pipeline was deleted. Collectors poll for updated remote configurations at the frequency you set in their remotecfg blocks.

  • If you discover the deleted pipeline before the collector’s next poll, you can copy the pipeline content from the Fleet Management interface.
    1. On the Inventory tab, click on one of the collectors that received the deleted pipeline. The details view opens.
    2. Switch to the Configuration tab and locate the pipeline content.
    3. Copy and paste the content into a blank configuration pipeline.
  • When the collector has already polled for an updated remote configuration, the deleted pipeline is unrecoverable. You must create a new one.

In both cases, you must also recreate the matching attributes that select the collectors receiving the pipeline.

Top-level configuration block gives error

Remote configuration does not support top-level configuration blocks. If you want to use a top-level block, you must add the block to the collector’s local configuration file.