Github url

telegraf

by influxdata

influxdata /telegraf

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

8.9K Stars 3.6K Forks Last release: 15 days ago (v1.14.5) MIT License 5.0K Commits 147 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Telegraf Circle CI Docker pulls

Telegraf is an agent for collecting, processing, aggregating, and writing metrics.

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.

Telegraf is plugin-driven and has the concept of 4 distinct plugin types:

  1. Input Plugins collect metrics from the system, services, or 3rd party APIs
  2. Processor Plugins transform, decorate, and/or filter metrics
  3. Aggregator Plugins create aggregate metrics (e.g. mean, min, max, quantiles, etc.)
  4. Output Plugins write metrics to various destinations

New plugins are designed to be easy to contribute, pull requests are welcomed and we work to incorporate as many pull requests as possible.

Try in Browser :rocket:

You can try Telegraf right in your browser in the Telegraf playground.

Contributing

There are many ways to contribute: - Fix and report bugs- Improve documentation- Review code and feature proposals- Answer questions and discuss here on github and on the Community Site- Contribute plugins- Contribute external plugins (experimental)

Minimum Requirements

Telegraf shares the same minimum requirements as Go: - Linux kernel version 2.6.23 or later - Windows 7 or later - FreeBSD 11.2 or later - MacOS 10.11 El Capitan or later

Installation:

You can download the binaries directly from the downloads page or from the releases section.

Ansible Role:

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

From Source:

Telegraf requires Go version 1.13 or newer, the Makefile requires GNU make.

  1. Install Go >=1.13 (1.14 recommended)
  2. Clone the Telegraf repository:
    cd ~/src git clone https://github.com/influxdata/telegraf.git
  3. Run
    make
    from the source directory
    cd ~/src/telegraf make

Changelog

View the changelog for the latest updates and changes by version.

Nightly Builds

These builds are generated from the master branch: - telegraf-nightly_darwin_amd64.tar.gz- telegraf_nightly_amd64.deb- telegraf_nightly_arm64.deb- telegraf-nightly.arm64.rpm- telegraf_nightly_armel.deb- telegraf-nightly.armel.rpm- telegraf_nightly_armhf.deb- telegraf-nightly.armv6hl.rpm- telegraf-nightly_freebsd_amd64.tar.gz- telegraf-nightly_freebsd_i386.tar.gz- telegraf_nightly_i386.deb- telegraf-nightly.i386.rpm- telegraf-nightly_linux_amd64.tar.gz- telegraf-nightly_linux_arm64.tar.gz- telegraf-nightly_linux_armel.tar.gz- telegraf-nightly_linux_armhf.tar.gz- telegraf-nightly_linux_i386.tar.gz- telegraf-nightly_linux_s390x.tar.gz- telegraf_nightly_s390x.deb- telegraf-nightly.s390x.rpm- telegraf-nightly_windows_amd64.zip- telegraf-nightly_windows_i386.zip- telegraf-nightly.x86_64.rpm- telegraf-static-nightly_linux_amd64.tar.gz

How to use it:

See usage with:

telegraf --help

Generate a telegraf config file:

telegraf config \> telegraf.conf

Generate config with only cpu input & influxdb output plugins defined:

telegraf --section-filter agent:inputs:outputs --input-filter cpu --output-filter influxdb config

Run a single telegraf collection, outputting 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

Documentation

Latest Release Documentation.

For documentation on the latest development code see the documentation index.

Input Plugins

Parsers

Serializers

Processor Plugins

Aggregator Plugins

Output Plugins

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.