# Grafana Alloy

Grafana Alloy is an open-source observability collector that collects, processes, and exports telemetry signals through native pipelines.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## 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

## Trace linkage: connect the dots between your app traces and database queries

DevFeed: [Trace linkage: connect the dots between your app traces and database queries](<https://devfeed.tech/articles/trace-linkage-connect-the-dots-between-your-app-traces-and-database-queries-116281.md>)

Original publisher: [Read original article](<https://grafana.com/blog/trace-linkage-connect-the-dots-between-your-app-traces-and-database-queries/>)

Author: Shirley

Published: 2026-11-03T15:05:03Z

Content type: release

Language: en

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

Topics: [observability](<https://devfeed.tech/topics/observability.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.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>), [application](<https://devfeed.tech/tags/application.md>), [database](<https://devfeed.tech/tags/database.md>), [database-observability](<https://devfeed.tech/tags/database-observability.md>), [execution](<https://devfeed.tech/tags/execution.md>), [explain](<https://devfeed.tech/tags/explain.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [history](<https://devfeed.tech/tags/history.md>), [logs](<https://devfeed.tech/tags/logs.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>), [performance](<https://devfeed.tech/tags/performance.md>), [plan](<https://devfeed.tech/tags/plan.md>), [queries](<https://devfeed.tech/tags/queries.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [tempo](<https://devfeed.tech/tags/tempo.md>), [text](<https://devfeed.tech/tags/text.md>), [trace](<https://devfeed.tech/tags/trace.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>)

### AI overview

Grafana Cloud Database Observability's trace linkage connects OpenTelemetry database spans to query context collected by Alloy. It uses query text, database system, and database name; spans with `db.query.text` or legacy `db.statement` may match without further application instrumentation. For more precise execution-level matches, optional sqlcommenter propagation places trace and span IDs in SQL comments, which Alloy extracts from query sample logs. Exact matches are best-effort: Alloy may miss short-lived executions or fail to poll them, sqlcommenter does not support every database engine and may affect database caches. When exact matching is unavailable, trace linkage accounts for differences in query formatting, comments, literals, and parameter placeholders to find matching query text, allowing users to inspect samples, historical performance, schema, and explain plans. Setup requires an OpenTelemetry-instrumented application sending traces to Grafana Cloud and Database Observability configured.

### Source excerpt

When an application request slows down, a trace can show a database call. Finding the database query behind it can be tedious, requiring you to switch between traces and database telemetry, as well as match timestamps or query text by hand. In Grafana Cloud, the Database Observability app already provides a window into all of your database telemetry, including query samples, performance history, and explain plan. But what if you could jump from that database call in the trace straight to its query details? OpenTelemetry database semantic conventions stabilized last year, giving us all a dependable shared language for describing database operations. That foundation has opened the door for what we call trace linkage, now Generally Available in Database Observability! What is trace linkage? With trace linkage, we try to provide a connection between OpenTelemetry-instrumented applications and database telemetry collected with Alloy. In other words, when you give us these previously-disjoint puzzle pieces, we'll do our best to provide you as much supporting information between these two elements as we can. And we'll do it without making you tediously piece together timestamps and logs. From a database span in a trace, you'll see a link on the query text. Clicking from there, the app searches for a connection between your database query and our opinionated view of your most relevant data in the Database Observability app. You can explore sampled query execution data or check out the query's historical performance, alongside that query's related schema and explain plan. This connection builds on the database attributes your OpenTelemetry instrumentation already emits. Grafana Cloud Traces, powered by Tempo, retain those attributes, and trace linkage uses the query text, database system, and database name to connect a database span to its supporting query context in Database Observability. We support the stable conventions like db.query.text and its legacy equivalent db.sta

## Instrumentation Hub in Grafana Cloud: start easier, stay in control

DevFeed: [Instrumentation Hub in Grafana Cloud: start easier, stay in control](<https://devfeed.tech/articles/instrumentation-hub-in-grafana-cloud-start-easier-stay-in-control-113326.md>)

Original publisher: [Read original article](<https://grafana.com/blog/instrumentation-hub-start-your-observability-journey-easier-and-still-stay-in-control/>)

Author: Fabian Stäber

Published: 2026-11-02T15:44:53Z

Content type: release

Language: en

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

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

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [alloy](<https://devfeed.tech/tags/alloy.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [ebpf](<https://devfeed.tech/tags/ebpf.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>), [helm](<https://devfeed.tech/tags/helm.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [observability](<https://devfeed.tech/tags/observability.md>), [observabilitycon](<https://devfeed.tech/tags/observabilitycon.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemetry-collector](<https://devfeed.tech/tags/opentelemetry-collector.md>), [opentelemetry-sdk](<https://devfeed.tech/tags/opentelemetry-sdk.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud's Instrumentation Hub is generally available for Kubernetes clusters running Linux. Install Alloy with a Helm command; it discovers workloads and shows what is instrumented. Teams can use the Grafana Cloud UI, API automation, or an LLM agent to select what telemetry to collect, then adjust scope and signals by namespace to manage coverage and spend. The Hub supports eBPF instrumentation and selective OpenTelemetry SDK injection, which the excerpt says adds runtime insight and can enrich baseline service visibility without extra collection layers or disruptive restarts. It also describes one-click Kubernetes Monitoring and populating Grafana Cloud's Knowledge Graph. The excerpt does not specify supported languages or deployment requirements beyond Linux Kubernetes.

### Source excerpt

It's no secret that getting started with observability can be much harder than it should be. That's why, at ObservabilityCon 2025, we introduced Instrumentation Hub: a guided, scalable way to roll out observability coverage while still keeping you in control. Today, we're excited to announce that Instrumentation Hub is now Generally Available in Grafana Cloud. As we hinted at before, this new iteration introduces selective OpenTelemetry SDK injection, giving you deeper runtime insights for a wide range of languages to complement eBPF instrumentation with a single click. What is the Instrumentation Hub? Instrumentation Hub makes the biggest bottleneck of starting with observability, instrumentation, faster and easier by leveraging open source eBPF and OTel injection. At Grafana Labs, we're champions of open-standards-based observability, but we also realize that getting meaningful coverage of your systems can often mean months of manual toil. Each layer requires its own instrumentation approach, balancing technology tradeoffs, and unique brittle steps. Organizational challenges exacerbate this process, making observability a moving target with uneven coverage, persistent blind spots, and ultimately leaving you wondering if the effort was worth the pain. We believe there's a better way. Instrumentation Hub is a control plane for remote discovery and selective auto-instrumentation. It helps you go from zero to meaningful telemetry in a matter of minutes by removing the bottleneck of having to apply instrumentation by hand. How Instrumentation Hub works The premise is simple: you run a single Helm command on your Kubernetes cluster to install Alloy, our distribution of the OpenTelemetry Collector. Once installed, Instrumentation Hub automatically catalogs everything that's running on the cluster, structured by namespace and technology. Teams can immediately see what exists, what's instrumented, and what isn't. Then, you use either the Grafana Cloud UI, an API automation

## Manage your OpenTelemetry Collectors with Fleet Management in Grafana Cloud

DevFeed: [Manage your OpenTelemetry Collectors with Fleet Management in Grafana Cloud](<https://devfeed.tech/articles/manage-your-opentelemetry-collectors-with-fleet-management-in-grafana-cloud-77315.md>)

Original publisher: [Read original article](<https://grafana.com/blog/manage-your-opentelemetry-collectors-with-fleet-management-in-grafana-cloud/>)

Author: Marko Bachvarovski

Published: 2026-10-08T14:04:56Z

Content type: article

Language: en

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

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

Tags: [analytics](<https://devfeed.tech/tags/analytics.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>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [logs](<https://devfeed.tech/tags/logs.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>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [telemetry-pipelines](<https://devfeed.tech/tags/telemetry-pipelines.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

Grafana Cloud Fleet Management now supports supported upstream OpenTelemetry Collector distributions through OpAMP, allowing teams to centrally manage collectors without migrating to Grafana Alloy. The article describes targeting YAML pipelines across collector fleets, Terraform-based configuration and enrollment, automatic monitoring, and configuration merging for reusable pipelines. It also explains how the gateway pattern can separate edge collection from shared processing.

### Source excerpt

If you've built your telemetry pipelines around OpenTelemetry Collectors, you've already invested in a collector distribution, YAML configuration, and a deployment model that fits your infrastructure. As that deployment grows, managing it means keeping shared configuration consistent, accommodating different workloads, and understanding whether your collectors are healthy. Fleet Management in Grafana Cloud brings those tasks together in one place. With support for the Open Agent Management Protocol (OpAMP) now generally available, you can bring supported OpenTelemetry Collector distributions into Fleet Management while continuing to use the OTel configuration language and components you already know. We started with Grafana Alloy, Grafana's distribution of the OpenTelemetry Collector. OpAMP support extends that management workflow to organizations running upstream OTel Collector distributions, so you can adopt centralized management without first migrating to Alloy. Keep your OTel configuration, manage it across your fleet For a platform team supporting multiple services or environments, collector configuration often includes both shared policies and workload-specific requirements. You might apply common processing across your fleet while enabling additional collection pipelines only for particular teams, services, or environments. Fleet Management lets you define those pipelines in OTel YAML and match them to the collectors that should run them. You can update a shared pipeline centrally and apply it across the matching collectors, reducing the work of maintaining configuration separately for each deployment. For teams using infrastructure as code, Terraform support brings this workflow into your existing processes. You can create pipelines with YAML configuration and register active collectors with Fleet Management, making configuration and enrollment part of a repeatable, version-controlled workflow. You also get visibility into the collectors running those pipel

## Grafana Turns Cypress Test Results Into Persistent Observability Data

DevFeed: [Grafana Turns Cypress Test Results Into Persistent Observability Data](<https://devfeed.tech/articles/grafana-turns-cypress-test-results-into-persistent-observability-data-59806.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/grafana-cypress-observability/>)

Author: Craig Risi

Published: 2026-09-25T12:00:00Z

Content type: tutorial

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Cypress](<https://devfeed.tech/topics/cypress.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana Cloud](<https://devfeed.tech/topics/grafana-cloud.md>), [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>)

Tags: [automated-testing](<https://devfeed.tech/tags/automated-testing.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [devops](<https://devfeed.tech/tags/devops.md>), [flaky-tests](<https://devfeed.tech/tags/flaky-tests.md>), [github-actions](<https://devfeed.tech/tags/github-actions.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>), [grafana-cypress-observability](<https://devfeed.tech/tags/grafana-cypress-observability.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>)

### AI overview

Grafana Labs describes a practical method for turning Cypress test results into Prometheus metrics and sending them to Grafana Cloud. Using Cypress lifecycle hooks, Pushgateway, and Grafana Alloy, teams can track failures, durations, flaky tests, and longer-term quality trends alongside application and infrastructure telemetry.

### Source excerpt

Grafana Labs has published a practical approach for monitoring Cypress test suites by converting test results into Prometheus metrics and sending them to Grafana Cloud. By Craig Risi