Slide 2 of 5

InfluxDB

InfluxDB to Grafana Cloud

For InfluxDB metrics, you can use either the InfluxDB exporter or Telegraf as a bridge to Grafana Cloud. Teams with existing InfluxDB infrastructure use these to send their metrics.

InfluxDB to Grafana Cloud flow

Option 1: InfluxDB exporter

Best when you want to keep existing InfluxDB writers unchanged.

  • No changes to your InfluxDB writers, and it accepts InfluxDB line protocol.
  • Converts the line protocol to Prometheus format and exposes it on a scrape endpoint. Prometheus scrapes the exporter and remote writes the metrics to Grafana Cloud.
  • Adds two components to run and maintain: the exporter and Prometheus.

Option 2: Telegraf

Best when you want a direct push model.

  • Pushes line protocol directly with Telegraf’s InfluxDB output plugin to the Grafana Cloud metrics endpoint, which converts it to Prometheus format. A Prometheus remote write output is also supported.
  • Adds Telegraf as a tool to manage in your setup.

Documentation

Script

If you have metrics in InfluxDB format, you have two main options for sending them to Grafana Cloud: the InfluxDB exporter and Telegraf.

The InfluxDB exporter acts as a bridge. It receives InfluxDB line protocol data and converts it to Prometheus format, exposing it on a scrape endpoint. Prometheus scrapes the exporter and remote writes those metrics to Grafana Cloud. This is useful if you have existing systems writing InfluxDB line protocol and you don’t want to modify them.

Telegraf is InfluxData’s collection agent. Its InfluxDB output plugin pushes line protocol straight to the Grafana Cloud metrics endpoint, which converts it to Prometheus format. Telegraf can also use a Prometheus remote write output instead. If you’re already using Telegraf or want a direct push-based approach, this is a good option.

The InfluxDB exporter fits when you want to keep your existing writers unchanged. Telegraf fits when you want a direct push model.

Keep in mind that InfluxDB and Prometheus have different data models, so some metrics may need mapping adjustments. Both tools handle common cases automatically, but complex schemas might need configuration.