Grafana Alloy collects operational data and sends it through configured processing steps to monitoring backends. It is useful when a team needs a managed collection path for signals such as application logs, rather than leaving every application to handle delivery separately. Existing Promtail users can also evaluate it as a replacement collector. The destination still owns retention and querying, while Alloy's configuration determines discovery, parsing and delivery behavior.
Deployment and operating notes
It is especially relevant to existing Promtail users: Grafana's migration documentation identifies Promtail's end of life as March 2, 2026 and provides a path to Alloy.
Migrate the stream, not just the config file
Inventory log discovery, labels, parsing stages, multiline handling, tenant headers, credentials and saved read positions. A configuration conversion does not establish identical output. Compare representative events for missing lines, duplicate lines, changed timestamps and label cardinality.
Rollout and rollback
Begin on a bounded group of nodes. Ensure only the intended collectors read and forward each stream, and decide how saved offsets are handled before replacing an agent. Keep a controlled rollback plan that does not replay an entire log history into production storage.
Compare Alloy and the OpenTelemetry Collector by required components, operational familiarity and backend integration. Neither choice eliminates the need for a retention and cost policy at the storage layer.
Sources & further reading
Spotted something that needs another look?
Help improve this page →