The plugin-driven server agent for collecting & reporting metrics.

go get


Telegraf Circle CI Docker pulls

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.


Linux deb and rpm Packages:


Latest (arm):

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 on setting up the repo. Once it is configured, you will be able to use this repo to install & update telegraf.

Linux tarballs:


FreeBSD tarball:


Ansible Role:

Ansible role:

OSX via Homebrew:

brew update
brew install telegraf

Windows Binaries (EXPERIMENTAL)


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
  4. Run cd $GOPATH/src/
  5. Run make

How to use it:

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


  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


  # 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


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:

Telegraf can also collect metrics via the following service plugins:

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


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