What problem does it solve?
Grafana Alloy configuration needs a consistent way to collect, transform, and forward metrics, logs, traces, and profiles while supporting Kubernetes discovery and remote backends without manual wiring for each signal type.
Core Features & Use Cases
- Define multi-signal pipelines: Configure collection for metrics, logs, traces, and profiles in one Alloy config.
- Scrape and discovery-driven routing: Use Kubernetes discovery and relabeling to target the right pods and enrich/export safely.
- Export to Grafana Cloud and compatible endpoints: Send telemetry via Prometheus remote_write, Loki push, and OTLP exporters with required auth.
- Troubleshoot and standardize collection: Apply processing steps (batching, relabeling, log parsing/labeling) and use known component patterns to reduce configuration drift.
Quick Start
Use the alloy skill to generate or validate a config.alloy that scrapes Kubernetes pods and forwards metrics to Prometheus remote write, logs to Loki, and traces to Tempo by referencing the relevant component blocks in your Alloy file.