# Bridging Alloy and OpenTelemetry: the OTel engine is now in Public Preview

DevFeed: [Bridging Alloy and OpenTelemetry: the OTel engine is now in Public Preview](<https://devfeed.tech/articles/bridging-alloy-and-opentelemetry-the-otel-engine-is-now-in-public-preview-116280.md>)

Original publisher: [Read original article](<https://grafana.com/blog/bridging-alloy-and-opentelemetry-the-otel-engine-is-now-in-public-preview/>)

Author: Bejal Lewis

Published: 2026-11-03T21:32:18Z

Content type: news

Language: en

Sources: [Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [observability pipelines](<https://devfeed.tech/topics/observability-pipelines.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>)

Tags: [alloy](<https://devfeed.tech/tags/alloy.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [bridging](<https://devfeed.tech/tags/bridging.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [collector](<https://devfeed.tech/tags/collector.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [embedded](<https://devfeed.tech/tags/embedded.md>), [engine](<https://devfeed.tech/tags/engine.md>), [engines](<https://devfeed.tech/tags/engines.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [fleet-management](<https://devfeed.tech/tags/fleet-management.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-alloy](<https://devfeed.tech/tags/grafana-alloy.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [installation](<https://devfeed.tech/tags/installation.md>), [logs](<https://devfeed.tech/tags/logs.md>), [loki](<https://devfeed.tech/tags/loki.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [otel](<https://devfeed.tech/tags/otel.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [traces](<https://devfeed.tech/tags/traces.md>)

## AI overview

Grafana Alloy's OTel engine reached Public Preview in Alloy v1.21.0, offering native OpenTelemetry Collector pipelines alongside Alloy's cross-ecosystem default engine. It runs standard collector YAML without translation; existing `otelcol` workflows can use `alloy otel`, and deployments are supported through the upstream Helm chart, OpenTelemetry Operator v0.153.0+, or Alloy packages in OTel mode. Fleet Management can centrally apply configuration through the experimental `otel-supervisor` command. The engines cannot pass data directly; the experimental `alloyengine` extension runs Alloy configuration inside the collector as a bridge, but the article says it is unsupported for production. Examples include Database Observability and cloud provider exporters; native collector components are still in progress. Planned OTel work includes support bundles, while default-engine work targets more reliable Prometheus remote write and Loki delivery.

## Source excerpt

Many Grafana Cloud customers love what Alloy offers them, but we're also seeing a growing base of users who feel the same way about the OpenTelemetry Collector. We want to make it easy for customers to make the decision that makes the most sense, regardless of their preference. When we introduced the OpenTelemetry engine for Grafana Alloy, we set out to give teams a way to run native OTLP pipelines without giving up the power and flexibility Alloy is known for. Since then we've kept building: ironing out service installation support, enabling Fleet Management, and folding in feedback from early users. Today, as of Alloy v1.21.0, we're happy to share that the OTel engine has moved into Public Preview, running right alongside the default engine you already know. In this post, we'll dig into when you'd reach for each engine, walk through some of the most interesting use cases we've seen so far, and give a preview of where both engines are headed next. The motivation behind each engine Before diving into specific new features, let's recap why we have two engines in Alloy. Default engine The default engine is a cross-ecosystem engine at its core; it's not tied to any single wire format or vendor. It can just as easily run a Prometheus pipeline, an OTLP pipeline, or a Loki pipeline, all defined using Alloy's own configuration syntax. That flexibility is what makes it a Swiss army knife: the same engine that scrapes Prometheus metrics can pull in logs over syslog for logs, ingest OTLP, scrape Prometheus metrics from embedded exporters, and route all of it to wherever it needs to go. OpenTelemetry engine There's a lot to like about being able to speak every ecosystem's language. But the telemetry landscape itself is moving in the opposite direction. Rather than translating between formats, the industry is increasingly converging on a single, shared model defined by the OpenTelemetry specification. That's what an OpenTelemetry Collector actually is: a pipeline that treats OT