Menu
Grafana Cloud

Application Observability Data Collector

Applications may send telemetry data directly to the Grafana Cloud OTLP gateway, but it is recommended to run Grafana Alloy or OpenTelemetry Collector for several reasons:

  1. Reliability: Grafana Alloy or OpenTelemetry Collector buffer data during issues with the remote endpoint, ensuring transmission after recovery. Without a data collector you could lose data.
  2. Cost control: Grafana Alloy aggregates and drops telemetry data to only send relevant data and reduce costs.
  3. Flexibility: Grafana Alloy simplifies changes to the telemetry destination. Users update the Alloy configuration rather than restarting applications, which is necessary for direct OTLP writing.

Two options exist: Grafana Alloy or the OpenTelemetry Collector. Both work with Application Observability, but Grafana support only extends to Grafana Alloy.

Application Observability - Architecture

We recommend Grafana Alloy (formerly Grafana Agent), a vendor-neutral distribution of the OpenTelemetry (OTel) Collector. Grafana Alloy is supported by Grafana and allows you to have a seamless correlation between Application and Infrastructure observability.

Grafana Alloy

Consult the Grafana Alloy documentation for the recommended and supported way to send telemetry data for infrastructure and applications to Grafana Cloud.

Grafana Alloy for Kubernetes

If your application is deployed in Kubernetes, it is recommended to deploy Grafana Alloy using the Kubernetes Monitoring helm chart and take advantage of both Application Observability and Kubernetes Monitoring solutions.

Consult the Kubernetes Monitoring with Grafana Alloy documentation for more information.

OpenTelemetry Collector

Alternatively, consult the Grafana OpenTelemetry Collector documentation to use the community supported OpenTelemetry Collector to send telemetry data to Grafana Cloud.