What problem does it solve?
Fleet Management and Alloy configuration are complex at scale because teams must distribute, update, and validate collector pipeline configurations across many hosts without restarting agents, and they need a safe way to target, roll out, and troubleshoot remote configs.
Core Features & Use Cases
- Remote pipeline distribution: Create and update named Alloy pipeline configurations and deliver them to matching collectors via Fleet Management.
- Targeting and staged rollouts: Use matchers and collector attributes to target pipelines to specific environments, teams, or canary hosts for safe rollouts.
- Troubleshooting and validation: Inspect collector remoteConfig status, interpret error messages, validate Alloy River syntax, and roll back revisions when needed.
- Use Case: Deploy a new Prometheus scrape pipeline to production nodes, validate in a canary collector, and then expand to the fleet while monitoring remoteConfigStatus and logs.
Quick Start
List all collectors with REMOTE_CONFIG_STATUS_FAILED and summarize each remoteConfigStatusMessage so I can prioritize fixes.
