Influxdata
/
influxdb
mirror of https://github.com/influxdata/influxdb.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Graphite

pull/7483/head
Hung Nguyen Viet 2016-10-20 18:52:14 +07:00
parent cc7b61d385
commit 1f26984181
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
services/graphite/README.md
View File

@ -1,4 +1,4 @@
# The graphite Input
# The Graphite Input
## A note on UDP/IP OS Buffer sizes
@ -13,7 +13,7 @@ Each Graphite input also performs internal batching of the points it receives, a
## Parsing Metrics
The graphite plugin allows measurements to be saved using the graphite line protocol. By default, enabling the graphite plugin will allow you to collect metrics and store them using the metric name as the measurement. If you send a metric named `servers.localhost.cpu.loadavg.10`, it will store the full metric name as the measurement with no extracted tags.
The Graphite plugin allows measurements to be saved using the Graphite line protocol. By default, enabling the Graphite plugin will allow you to collect metrics and store them using the metric name as the measurement. If you send a metric named `servers.localhost.cpu.loadavg.10`, it will store the full metric name as the measurement with no extracted tags.
While this default setup works, it is not the ideal way to store measurements in InfluxDB since it does not take advantage of tags. It also will not perform optimally with large dataset sizes since queries will be forced to use regexes which is known to not scale well.
@ -21,7 +21,7 @@ To extract tags from metrics, one or more templates must be configured to parse
## Templates
Templates allow matching parts of a metric name to be used as tag keys in the stored metric. They have a similar format to graphite metric names. The values in between the separators are used as the tag keys. The location of the tag key that matches the same position as the graphite metric section is used as the value. If there is no value, the graphite portion is skipped.
Templates allow matching parts of a metric name to be used as tag keys in the stored metric. They have a similar format to Graphite metric names. The values in between the separators are used as the tag keys. The location of the tag key that matches the same position as the Graphite metric section is used as the value. If there is no value, the Graphite portion is skipped.
The special value _measurement_ is used to define the measurement name. It can have a trailing `*` to indicate that the remainder of the metric should be used. If a _measurement_ is not specified, the full metric name is used.
@ -170,12 +170,12 @@ If you need to add the same set of tags to all metrics, you can define them glob
# filter + template with field key
"stats.* .host.measurement.field",
# default template. Ignore the first graphite component "servers"
# default template. Ignore the first Graphite component "servers"
".measurement*",
]
```
## Two graphite listeners, UDP & TCP, Config
## Two Graphite listeners, UDP & TCP, Config
```
[[graphite]]