A Prometheus exporter that accepts metrics via the Graphite plaintext protocol and converts them for Prometheus consumption.
Graphite Exporter is a Prometheus exporter that accepts metrics in the Graphite plaintext protocol and converts them into the Prometheus exposition format. It acts as a bridge, allowing users to integrate existing Graphite metrics or metrics not covered by core Prometheus exporters into their Prometheus monitoring stack. The exporter supports both TCP and UDP for metric ingestion and includes configurable mapping for transforming Graphite metrics into labeled Prometheus metrics.
DevOps engineers, SREs, and developers who have existing Graphite monitoring setups and want to integrate those metrics into Prometheus, or who need to export metrics not covered by other Prometheus exporters.
It provides a dedicated, configurable bridge for Graphite metrics, supporting flexible mapping, tagged carbon format, and easy deployment via Docker. Unlike generic bridges, it avoids information loss and conflicts associated with client library Graphite bridges.
Server that accepts metrics via the Graphite protocol and exports them as Prometheus metrics
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses YAML configuration to transform dot-separated Graphite metrics into labeled Prometheus metrics, offering granular control similar to statsd_exporter for precise naming and labeling.
Accepts metrics in the tagged carbon format, parsing labels and handling inconsistencies, which is essential for modern Graphite setups and prevents data loss.
Provided as a Docker image, enabling quick setup and self-hosting with minimal effort, as shown in the example Docker run command.
Automatically expires unused metrics after a configurable time via the --graphite.sample-expiry flag, preventing unbounded memory usage.
After version 0.2.0, configuration syntax changed, requiring conversion with external tools and potentially disrupting existing setups, as admitted in the README.
Does not support all parsing features from statsd_exporter, such as timer_type options, limiting advanced use cases for certain metric types.
Explicitly does not work with Java or Python client Graphite bridges, forcing users to adopt direct scraping or alternative pushing methods, which adds complexity.