dom
/
telegraf
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Root directory cleanup

This commit is contained in:
Cameron Sparr 2016-02-18 13:37:36 -07:00 committed by Michele Fadda
parent 87027fbacd
commit 132f89e3fe
22 changed files with 30 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -8,9 +8,9 @@ format that they would like to parse. Currently supports: "json", "influx", and
- Users of message broker and file output plugins can now choose what data format - Users of message broker and file output plugins can now choose what data format
they would like to output. Currently supports: "influx" and "graphite" they would like to output. Currently supports: "influx" and "graphite"
- More info on parsing _incoming_ data formats can be found - More info on parsing _incoming_ data formats can be found
[here](https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md) [here](https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md)
- More info on serializing _outgoing_ data formats can be found - More info on serializing _outgoing_ data formats can be found
[here](https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md) [here](https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md)
- Telegraf now has an option `flush_buffer_when_full` that will flush the - Telegraf now has an option `flush_buffer_when_full` that will flush the
metric buffer whenever it fills up for each output, rather than dropping metric buffer whenever it fills up for each output, rather than dropping
points and only flushing on a set time interval. This will default to `true` points and only flushing on a set time interval. This will default to `true`

8
CONTRIBUTING.md
View File

@ -101,7 +101,7 @@ Some input plugins (such as
[exec](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/exec)) [exec](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/exec))
accept arbitrary input data formats. An overview of these data formats can accept arbitrary input data formats. An overview of these data formats can
be found be found
[here](https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md). [here](https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md).
In order to enable this, you must specify a `SetParser(parser parsers.Parser)` In order to enable this, you must specify a `SetParser(parser parsers.Parser)`
function on the plugin object (see the exec plugin for an example), as well as function on the plugin object (see the exec plugin for an example), as well as
@ -117,7 +117,7 @@ You should also add the following to your SampleConfig() return:
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
``` ```
@ -230,7 +230,7 @@ Some output plugins (such as
[file](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/file)) [file](https://github.com/influxdata/telegraf/tree/master/plugins/outputs/file))
can write arbitrary output data formats. An overview of these data formats can can write arbitrary output data formats. An overview of these data formats can
be found be found
[here](https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md). [here](https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md).
In order to enable this, you must specify a In order to enable this, you must specify a
`SetSerializer(serializer serializers.Serializer)` `SetSerializer(serializer serializers.Serializer)`
@ -247,7 +247,7 @@ You should also add the following to your SampleConfig() return:
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
``` ```

2
README.md
View File

@ -141,7 +141,7 @@ Examples:
## Configuration ## Configuration
See the [configuration guide](CONFIGURATION.md) for a rundown of the more advanced See the [configuration guide](docs/CONFIGURATION.md) for a rundown of the more advanced
configuration options. configuration options.
## Supported Input Plugins ## Supported Input Plugins

0
CONFIGURATION.md → docs/CONFIGURATION.md
View File

8
DATA_FORMATS_INPUT.md → docs/DATA_FORMATS_INPUT.md
View File

@ -34,7 +34,7 @@ example, in the exec plugin:
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "json" data_format = "json"
### Additional configuration options go here ### Additional configuration options go here
@ -61,7 +61,7 @@ metrics are parsed directly into Telegraf metrics.
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
``` ```
@ -106,7 +106,7 @@ For example, if you had this configuration:
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "json" data_format = "json"
### List of tag names to extract from top-level of JSON server response ### List of tag names to extract from top-level of JSON server response
@ -250,7 +250,7 @@ There are many more options available,
### Data format to consume. This can be "json", "influx" or "graphite" (line-protocol) ### Data format to consume. This can be "json", "influx" or "graphite" (line-protocol)
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "graphite" data_format = "graphite"
### This string will be used to join the matched values. ### This string will be used to join the matched values.

6
DATA_FORMATS_OUTPUT.md → docs/DATA_FORMATS_OUTPUT.md
View File

@ -32,7 +32,7 @@ config option, for example, in the `file` output plugin:
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
### Additional configuration options go here ### Additional configuration options go here
@ -56,7 +56,7 @@ metrics are serialized directly into InfluxDB line-protocol.
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
``` ```
@ -90,7 +90,7 @@ tars.cpu-total.us-east-1.cpu.usage_idle 98.09 1455320690
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
prefix = "telegraf" prefix = "telegraf"

0
LICENSE_OF_DEPENDENCIES.md → docs/LICENSE_OF_DEPENDENCIES.md
View File

2
plugins/inputs/exec/exec.go
View File

@ -23,7 +23,7 @@ const sampleConfig = `
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
` `

2
plugins/inputs/kafka_consumer/README.md
View File

@ -25,7 +25,7 @@ from the same topic in parallel.
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
``` ```

2
plugins/inputs/kafka_consumer/kafka_consumer.go
View File

@ -56,7 +56,7 @@ var sampleConfig = `
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
` `

4
plugins/inputs/mqtt_consumer/README.md
View File

@ -3,7 +3,7 @@
The [MQTT](http://mqtt.org/) consumer plugin reads from The [MQTT](http://mqtt.org/) consumer plugin reads from
specified MQTT topics and adds messages to InfluxDB. specified MQTT topics and adds messages to InfluxDB.
The plugin expects messages in the The plugin expects messages in the
[Telegraf Input Data Formats](https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md). [Telegraf Input Data Formats](https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md).
### Configuration: ### Configuration:
@ -38,7 +38,7 @@ The plugin expects messages in the
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
``` ```

2
plugins/inputs/mqtt_consumer/mqtt_consumer.go
View File

@ -71,7 +71,7 @@ var sampleConfig = `
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
` `

4
plugins/inputs/nats_consumer/README.md
View File

@ -2,7 +2,7 @@
The [NATS](http://www.nats.io/about/) consumer plugin reads from The [NATS](http://www.nats.io/about/) consumer plugin reads from
specified NATS subjects and adds messages to InfluxDB. The plugin expects messages specified NATS subjects and adds messages to InfluxDB. The plugin expects messages
in the [Telegraf Input Data Formats](https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md). in the [Telegraf Input Data Formats](https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md).
A [Queue Group](http://www.nats.io/documentation/concepts/nats-queueing/) A [Queue Group](http://www.nats.io/documentation/concepts/nats-queueing/)
is used when subscribing to subjects so multiple instances of telegraf can read is used when subscribing to subjects so multiple instances of telegraf can read
from a NATS cluster in parallel. from a NATS cluster in parallel.
@ -26,6 +26,6 @@ from a NATS cluster in parallel.
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
``` ```

2
plugins/inputs/nats_consumer/nats_consumer.go
View File

@ -58,7 +58,7 @@ var sampleConfig = `
### Data format to consume. This can be "json", "influx" or "graphite" ### Data format to consume. This can be "json", "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
data_format = "influx" data_format = "influx"
` `

2
plugins/inputs/statsd/README.md
View File

@ -22,7 +22,7 @@
convert_names = true convert_names = true
### Statsd data translation templates, more info can be read here: ### Statsd data translation templates, more info can be read here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md#graphite ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md#graphite
# templates = [ # templates = [
# "cpu.* measurement*" # "cpu.* measurement*"
# ] # ]

2
plugins/inputs/statsd/statsd.go
View File

@ -140,7 +140,7 @@ const sampleConfig = `
convert_names = true convert_names = true
### Statsd data translation templates, more info can be read here: ### Statsd data translation templates, more info can be read here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_INPUT.md#graphite ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md#graphite
# templates = [ # templates = [
# "cpu.* measurement*" # "cpu.* measurement*"
# ] # ]

2
plugins/outputs/amqp/amqp.go
View File

@ -77,7 +77,7 @@ var sampleConfig = `
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
` `

2
plugins/outputs/file/file.go
View File

@ -26,7 +26,7 @@ var sampleConfig = `
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
` `

2
plugins/outputs/kafka/kafka.go
View File

@ -63,7 +63,7 @@ var sampleConfig = `
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
` `

2
plugins/outputs/mqtt/mqtt.go
View File

@ -35,7 +35,7 @@ var sampleConfig = `
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
` `

2
plugins/outputs/nsq/nsq.go
View File

@ -27,7 +27,7 @@ var sampleConfig = `
### Data format to output. This can be "influx" or "graphite" ### Data format to output. This can be "influx" or "graphite"
### Each data format has it's own unique set of configuration options, read ### Each data format has it's own unique set of configuration options, read
### more about them here: ### more about them here:
### https://github.com/influxdata/telegraf/blob/master/DATA_FORMATS_OUTPUT.md ### https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_OUTPUT.md
data_format = "influx" data_format = "influx"
` `

0
build.py → scripts/build.py
View File