Grafana Alloy v1.14.0 introduces an experimental OpenTelemetry engine that lets users configure Alloy using standard upstream OpenTelemetry Collector YAML. This opt-in feature runs alongside the existing default engine, meaning current setups are unaffected. A new `otel` CLI subcommand invokes the new engine, and an Alloy engine extension allows both pipelines to run in parallel within a single Alloy instance. The release is the first step toward making Alloy more OpenTelemetry-native, with future work planned to align operational parity between the two engines, including Fleet Management support.
Table of contents
A note on terminologyWhy this mattersWhat is included in the releaseWhat this means for existing Alloy usersRoadmap and expectationsSort: