You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Simon Pasquier d3c993c948
Build ARM container images (#102)
2 weeks ago
.circleci Build ARM container images (#102) 2 weeks ago
e2e Read metrics for #90 repro from file 1 month ago
vendor update logrus for AIX support 3 weeks ago
.dockerignore Build ARM container images (#102) 2 weeks ago
.gitignore New release process using docker, circleci and a centralized building tool 3 years ago
.golangci.yml Add .golangci.yml 2 months ago
.promu.yml *: bump Go version to 1.12 2 months ago
CHANGELOG.md Bump to 0.6.2 1 month ago
CONTRIBUTING.md Remove AUTHORS.md reference from CONTRIBUTING.md 2 years ago
Dockerfile Build ARM container images (#102) 2 weeks ago
LICENSE Initial commit of the Graphite Exporter. 4 years ago
MAINTAINERS.md Make MR maintainer (#35) 1 year ago
Makefile Build ARM container images (#102) 2 weeks ago
Makefile.common makefile: update Makefile.common with newer version 3 weeks ago
NOTICE Initial commit of the Graphite Exporter. 4 years ago
README.md Fix typo in documentation 2 months ago
VERSION Bump to 0.6.2 1 month ago
go.mod update logrus for AIX support 3 weeks ago
go.sum update logrus for AIX support 3 weeks ago
main.go Serialize processing of samples 1 month ago
main_test.go Serialize processing of samples 1 month ago

README.md

Graphite Exporter Build Status

CircleCI Docker Repository on Quay Docker Pulls

An exporter for metrics exported in the Graphite plaintext protocol. It accepts data over both TCP and UDP, and transforms and exposes them for consumption by Prometheus.

This exporter is useful for exporting metrics from existing Graphite setups, as well as for metrics which are not covered by the core Prometheus exporters such as the Node Exporter.

Usage

make
./graphite_exporter

Configure existing monitoring to send Graphite plaintext data to port 9109 on UDP or TCP. As a simple demonstration:

echo "test_tcp 1234 $(date +%s)" | nc localhost 9109
echo "test_udp 1234 $(date +%s)" | nc -u -w1 localhost 9109

Metrics will be available on http://localhost:9108/metrics.

To avoid using unbounded memory, metrics will be garbage collected five minutes after they are last pushed to. This is configurable with the --graphite.sample-expiry flag.

Metric Mapping and Configuration

Please note there has been a breaking change in configuration after version 0.2.0. The YAML style config from statsd_exporter is now used. See conversion instructions below

YAML Config

The graphite_exporter can be configured to translate specific dot-separated graphite metrics into labeled Prometheus metrics via YAML configuration file. This file shares syntax and logic with statsd_exporter. Please follow the statsd_exporter documentation for usage information. However, graphite_exporter does not support all parsing features at this time. Any feature based on the ‘timer_type’ option will not function. Otherwise, regex matching, groups, match/drop behavior, should work as expected.

Metrics that don’t match any mapping in the configuration file are translated into Prometheus metrics without any labels and with names in which every non-alphanumeric character except _ and : is replaced with _.

If you have a very large set of metrics you may want to skip the ones that don’t match the mapping configuration. If that is the case you can force this behaviour using the -graphite.mapping-strict-match flag, and it will only store those metrics you really want.

An example mapping configuration:

mappings:
- match: test.dispatcher.*.*.*
  name: dispatcher_events_total
  labels:
    action: $2
    job: test_dispatcher
    outcome: $3
    processor: $1
- match: '*.signup.*.*'
  name: signup_events_total
  labels:
    job: ${1}_server
    outcome: $3
    provider: $2

This would transform these example graphite metrics into Prometheus metrics as follows:

test.dispatcher.FooProcessor.send.success
 => dispatcher_events_total{processor="FooProcessor", action="send", outcome="success", job="test_dispatcher"}

foo_product.signup.facebook.failure
 => signup_events_total{provider="facebook", outcome="failure", job="foo_product_server"}

test.web-server.foo.bar
 => test_web__server_foo_bar{}

Conversion from legacy configuration

If you have an existing config file using the legacy mapping syntax, you may use statsd-exporter-convert to update to the new YAML based syntax. Here we convert the old example synatx:

$ go get -u github.com/bakins/statsd-exporter-convert

$ cat example.conf
test.dispatcher.*.*.*
name="dispatcher_events_total"
processor="$1"
action="$2"
outcome="$3"
job="test_dispatcher"

*.signup.*.*
name="signup_events_total"
provider="$2"
outcome="$3"
job="${1}_server"

$ statsd-exporter-convert example.conf
mappings:
- match: test.dispatcher.*.*.*
  name: dispatcher_events_total
  labels:
    action: $2
    job: test_dispatcher
    outcome: $3
    processor: $1
- match: '*.signup.*.*'
  name: signup_events_total
  labels:
    job: ${1}_server
    outcome: $3
    provider: $2
````

## Using Docker

You can deploy this exporter using the [prom/graphite-exporter][hub] Docker image.

For example:

```bash
docker pull prom/graphite-exporter

docker run -d -p 9108:9108 -p 9109:9109 -p 9109:9109/udp \
        -v ${PWD}/graphite_mapping.conf:/tmp/graphite_mapping.conf \
        prom/graphite-exporter --graphite.mapping-config=/tmp/graphite_mapping.conf