Documentation Grafana Cloud Instrument and send data Fleet Management Manage your fleet Pipelines View pipeline history

View configuration pipeline history

Grafana Fleet Management tracks changes to configuration pipelines and displays them in the Pipelines history feature on the Remote configuration tab. With pipeline history, your team can collaborate more efficiently, ensure audit compliance, and troubleshoot issues caused by configuration changes.

Use the Pipelines history view for a high-level overview of all changes to your pipelines in reverse chronological order. Each event is a snapshot of the configuration pipeline and its matching attributes at the time the change was made. The Pipelines history log tracks creation and deletion of pipelines, changes to configuration content, and modifications to matching attributes.

You can review changes for a specific pipeline by searching the log for a pipeline name, ID, or matching attribute. To view changes to configuration content, click the History details button in an event row and examine the pipeline on its own or compare it with another version of the same pipeline. Changes to matching attributes can be seen on the log page or in the History details page.

Compare versions of configuration pipelines

From the History details page, choose a view for comparing pipeline versions:

• The Single view displays only the selected pipeline version.
• The Split view displays two versions side-by-side without additional formatting.
• The Diff view displays two versions side-by-side with the differences highlighted.

Select the versions you want to compare from the dropdown lists.

Restore configuration pipeline versions

To revert to another version of an existing pipeline, click the Restore button above that version’s display window. In the Restore Pipeline Version window, review the configuration version to make sure it’s the one you want, select the matching attributes to assign to the restored version, and click Restore.

How it works

When you restore a pipeline version, the pipeline content, state, and attributes are affected:

• Restoring a pipeline version overwrites the configuration of the current pipeline.
• A restored pipeline is set to the same Active or Inactive state as the pipeline it overwrites.
• When a pipeline version is restored, its matching attributes can also be restored, or the matching attributes from the overwritten pipeline can be persisted in the restored version.

Troubleshoot pipeline issues

Refer to Troubleshoot configuration pipeline issues for ideas on how to use Pipelines history to diagnose problems.