A server that accepts InfluxDB metrics via HTTP/UDP and exports them in Prometheus format.
The InfluxDB Exporter is a Prometheus exporter that collects metrics formatted in the InfluxDB line protocol, transforms them into Prometheus-compatible metrics, and exposes them via HTTP endpoints for Prometheus to scrape. It acts as a bridge, enabling systems that output metrics to InfluxDB to be monitored by Prometheus without altering existing metric pipelines. It supports float, integer, and boolean fields, converting InfluxDB tags to Prometheus labels.
Developers and operators who have existing systems or applications that send metrics in the InfluxDB line protocol (version 0.9.0+) and want to integrate that data into a Prometheus monitoring stack. This is particularly useful for users of Telegraf or other tools that output to InfluxDB.
Developers choose this exporter for its simplicity and direct compatibility, allowing a seamless integration between InfluxDB-based metric sources and Prometheus without requiring changes to the source applications. Its unique selling point is acting as a drop-in InfluxDB server endpoint that translates protocols, supporting both HTTP and UDP ingestion.
A server that accepts InfluxDB metrics via the HTTP API and exports them via HTTP for Prometheus consumption
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Accepts metrics via both HTTP API and UDP socket in InfluxDB line protocol format, making it versatile for different data sources like network devices or legacy systems.
Can be configured as an output destination in Telegraf, allowing easy bridging of metrics to Prometheus without modifying existing Telegraf pipelines extensively.
Optional --timestamps flag preserves original metric timestamps in Prometheus exposition, useful for historical accuracy in monitoring scenarios.
Automatically converts InfluxDB tags to Prometheus labels, ensuring compatibility and structured metric metadata without manual intervention.
Experimental support for InfluxDB v2 ignores auth and metadata components, limiting its use in modern setups requiring security and organization, as admitted in the README.
When using timestamps, if metrics are submitted multiple times between scrapes, only the last value is stored, potentially leading to data loss for frequently updated metrics, as noted in the timestamp section.
Telegraf's outputs.prometheus_client plugin can serve the same purpose, making the influxdb_exporter an unnecessary extra component in deployments where Telegraf is already used, as highlighted in the alternatives section.