alloy

You configure unified telemetry pipelines by writing Alloy configuration language syntax to define modular components that collect metrics, logs, traces, and profiles. This unifies telemetry collection into a single config-driven pipeline, simplifying deployment across environments.

Yes, you can route collected telemetry data to Prometheus, Loki, Tempo, or Pyroscope. You build end-to-end pipelines using the Alloy config language to forward metrics, logs, traces, and profiles to these destinations, centralizing observability.

The best way to manage observability pipelines across a fleet is using Alloy's clustering and fleet remote config features. This config-driven approach applies unified telemetry collection across multi-service applications, reducing configuration drift.

Yes, Grafana Alloy supports OpenTelemetry collection. It unifies telemetry signals including metrics, logs, traces, and profiles into a single configurable pipeline, compatible with cloud-native deployments using OpenTelemetry standards.

You import modules by using the Alloy configuration language syntax, which supports modular component patterns. This allows you to define reusable telemetry pipeline components for metrics, logs, and traces across your services.