mirrors/statsd_exporter
1
0
Fork 1
mirror of https://github.com/prometheus/statsd_exporter.git synced 2024-11-25 16:51:00 +00:00
Code Issues Projects Releases Packages Wiki Activity

Merge pull request #16 from prometheus/document-no-statsd-case

Browse source 
Document use-case without any StatsD server.
This commit is contained in:
Julius Volz 2015-06-18 20:15:14 +02:00
commit e0bf2be66a
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -5,6 +5,8 @@ StatsD-Bridge receives StatsD-style metrics and exports them as Prometheus metri
## Overview ## Overview
### With StatsD
To pipe metrics from an existing StatsD environment into Prometheus, configure To pipe metrics from an existing StatsD environment into Prometheus, configure
StatsD's repeater backend to repeat all received packets to a StatsD-Bridge StatsD's repeater backend to repeat all received packets to a StatsD-Bridge
process. This bridge translates StatsD metrics to Prometheus metrics via process. This bridge translates StatsD metrics to Prometheus metrics via
@ -14,6 +16,16 @@ configured mapping rules.
| StatsD |---(UDP repeater)--->| StatsD-Bridge |<---(scrape /metrics)---| Prometheus | | StatsD |---(UDP repeater)--->| StatsD-Bridge |<---(scrape /metrics)---| Prometheus |
+----------+ +-----------------+ +--------------+ +----------+ +-----------------+ +--------------+
### Without StatsD
Since the StatsD bridge uses the same UDP protocol as StatsD itself, you can
also configure your applications to send StatsD metrics directly to the bridge.
In that case, you don't need to run a StatsD server anymore.
We recommend this only as an intermediate solution and recommend switching to
[native Prometheus instrumentation](http://prometheus.io/docs/instrumenting/clientlibs/)
in the long term.
## Building and Running ## Building and Running
$ go build $ go build