Go to file
Cameron Sparr e619493ece Implementing generic parser plugins and documentation
This constitutes a large change in how we will parse different data
formats going forward (for the plugins that support it)

This is working off @henrypfhu's changes.
2016-02-08 21:08:44 -07:00
agent Throughout telegraf, use telegraf.Metric rather than client.Point 2016-01-27 23:47:32 -07:00
cmd/telegraf Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
etc Change [tags] to [global_tags] to deal with toml bug 2016-02-08 16:20:47 -07:00
internal Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
plugins Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
scripts Try ping plugin with -n and -s options added 2016-02-06 23:09:29 -07:00
testutil Throughout telegraf, use telegraf.Metric rather than client.Point 2016-01-27 23:47:32 -07:00
.gitignore Added a `build.py` script for compiling and packaging. Added post and pre install scripts to handle installation and upgrades in a cleaner way. Minor fixes to the init script and service unit file. 2016-01-08 15:28:33 -06:00
CHANGELOG.md Change [tags] to [global_tags] to deal with toml bug 2016-02-08 16:20:47 -07:00
CONFIGURATION.md Change [tags] to [global_tags] to deal with toml bug 2016-02-08 16:20:47 -07:00
CONTRIBUTING.md Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
DATA_FORMATS_INPUT.md Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
Godeps Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
Godeps_windows Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
LICENSE Initial commit 2015-04-01 09:28:44 -07:00
LICENSE_OF_DEPENDENCIES.md Implement Glob matching for pass/drop filters 2015-12-07 16:58:31 -07:00
Makefile Add a make command with CGO disabled 2016-02-04 17:33:40 -07:00
README.md Add Graphite line protocol parsing to exec plugin 2016-02-08 17:12:28 -07:00
accumulator.go Create public models for telegraf metrics, accumlator, plugins 2016-01-27 15:42:50 -07:00
build.py Backporting fixes from the influxdb build script, along with a few improvements: 2016-01-25 15:13:55 -07:00
circle.yml renaming plugins -> inputs 2016-01-07 15:04:30 -07:00
input.go Create public models for telegraf metrics, accumlator, plugins 2016-01-27 15:42:50 -07:00
metric.go Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
metric_test.go Implementing generic parser plugins and documentation 2016-02-08 21:08:44 -07:00
output.go Throughout telegraf, use telegraf.Metric rather than client.Point 2016-01-27 23:47:32 -07:00

README.md

Telegraf Circle CI

Telegraf is an agent written in Go for collecting metrics from the system it's running on, or from other services, and writing them into InfluxDB or other outputs.

Design goals are to have a minimal memory footprint with a plugin system so that developers in the community can easily add support for collecting metrics from well known services (like Hadoop, Postgres, or Redis) and third party APIs (like Mailchimp, AWS CloudWatch, or Google Analytics).

New input and output plugins are designed to be easy to contribute, we'll eagerly accept pull requests and will manage the set of plugins that Telegraf supports. See the contributing guide for instructions on writing new plugins.

Installation:

NOTE: Telegraf 0.10.x is not backwards-compatible with previous versions of telegraf, both in the database layout and the configuration file. 0.2.x will continue to be supported, see below for download links.

For more details on the differences between Telegraf 0.2.x and 0.10.x, see the release blog post.

Linux deb and rpm Packages:

Latest:

0.2.x:

Package Instructions:
  • Telegraf binary is installed in /usr/bin/telegraf
  • Telegraf daemon configuration file is in /etc/telegraf/telegraf.conf
  • On sysv systems, the telegraf daemon can be controlled via service telegraf [action]
  • On systemd systems (such as Ubuntu 15+), the telegraf daemon can be controlled via systemctl [action] telegraf

yum/apt Repositories:

There is a yum/apt repo available for the whole InfluxData stack, see here for instructions, replacing the influxdb package name with telegraf.

Linux tarballs:

Latest:

0.2.x:

tarball Instructions:

To install the full directory structure with config file, run:

sudo tar -C / -xvf ./telegraf-0.10.2-1_linux_amd64.tar.gz

To extract only the binary, run:

tar -zxvf telegraf-0.10.2-1_linux_amd64.tar.gz --strip-components=3 ./usr/bin/telegraf

Ansible Role:

Ansible role: https://github.com/rossmcdonald/telegraf

OSX via Homebrew:

brew update
brew install telegraf

From Source:

Telegraf manages dependencies via gdm, which gets installed via the Makefile if you don't have it already. You also must build with golang version 1.5+.

  1. Install Go
  2. Setup your GOPATH
  3. Run go get github.com/influxdata/telegraf
  4. Run cd $GOPATH/src/github.com/influxdata/telegraf
  5. Run make

How to use it:

$ telegraf -help
Telegraf, The plugin-driven server agent for collecting and reporting metrics.

Usage:

  telegraf <flags>

The flags are:

  -config <file>     configuration file to load
  -test              gather metrics once, print them to stdout, and exit
  -sample-config     print out full sample configuration to stdout
  -config-directory  directory containing additional *.conf files
  -input-filter      filter the input plugins to enable, separator is :
  -output-filter     filter the output plugins to enable, separator is :
  -usage             print usage for a plugin, ie, 'telegraf -usage mysql'
  -debug             print metrics as they're generated to stdout
  -quiet             run in quiet mode
  -version           print the version to stdout

Examples:

  # generate a telegraf config file:
  telegraf -sample-config > telegraf.conf

  # generate config with only cpu input & influxdb output plugins defined
  telegraf -sample-config -input-filter cpu -output-filter influxdb

  # run a single telegraf collection, outputing metrics to stdout
  telegraf -config telegraf.conf -test

  # run telegraf with all plugins defined in config file
  telegraf -config telegraf.conf

  # run telegraf, enabling the cpu & memory input, and influxdb output plugins
  telegraf -config telegraf.conf -input-filter cpu:mem -output-filter influxdb

Configuration

See the configuration guide for a rundown of the more advanced configuration options.

Supported Input Plugins

Telegraf currently has support for collecting metrics from many sources. For more information on each, please look at the directory of the same name in plugins/inputs.

Currently implemented sources:

  • aerospike
  • apache
  • bcache
  • couchdb
  • disque
  • docker
  • elasticsearch
  • exec (generic executable plugin, support JSON, influx and graphite)
  • haproxy
  • httpjson (generic JSON-emitting http service plugin)
  • influxdb
  • jolokia
  • leofs
  • lustre2
  • mailchimp
  • memcached
  • mongodb
  • mysql
  • nginx
  • nsq
  • phpfpm
  • phusion passenger
  • ping
  • postgresql
  • powerdns
  • procstat
  • prometheus
  • puppetagent
  • rabbitmq
  • redis
  • rethinkdb
  • sql server (microsoft)
  • twemproxy
  • zfs
  • zookeeper
  • sensors
  • snmp
  • win_perf_counters (windows performance counters)
  • system
    • cpu
    • mem
    • net
    • netstat
    • disk
    • diskio
    • swap

Telegraf can also collect metrics via the following service plugins:

  • statsd
  • kafka_consumer
  • github_webhooks

We'll be adding support for many more over the coming months. Read on if you want to add support for another service or third-party API.

Supported Output Plugins

  • influxdb
  • amon
  • amqp
  • aws kinesis
  • aws cloudwatch
  • datadog
  • graphite
  • kafka
  • librato
  • mqtt
  • nsq
  • opentsdb
  • prometheus
  • riemann

Contributing

Please see the contributing guide for details on contributing a plugin to Telegraf.