telegraf

package module
v0.2.2 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Nov 18, 2015 License: MIT Imports: 19 Imported by: 0

README

Telegraf - A native agent for InfluxDB 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.

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).

We'll eagerly accept pull requests for new plugins and will manage the set of plugins that Telegraf supports. See the contributing guide for instructions on writing new plugins.

Installation:

Linux deb and rpm packages:

Latest:

Package instructions:
  • Telegraf binary is installed in /opt/telegraf/telegraf
  • Telegraf daemon configuration file is in /etc/opt/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
Linux binaries:

Latest:

Binary instructions:

These are standalone binaries that can be unpacked and executed on any linux system. They can be unpacked and renamed in a location such as /usr/local/bin for convenience. A config file will need to be generated, see "How to use it" below.

OSX via Homebrew:
brew update
brew install telegraf
From Source:

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

  1. Install Go
  2. Setup your GOPATH
  3. Run go get github.com/influxdb/telegraf
  4. Run cd $GOPATH/src/github.com/influxdb/telegraf
  5. Run make
How to use it:
  • Run telegraf -sample-config > telegraf.conf to create an initial configuration.
  • Or run telegraf -sample-config -filter cpu:mem -outputfilter influxdb > telegraf.conf. to create a config file with only CPU and memory plugins defined, and InfluxDB output defined.
  • Edit the configuration to match your needs.
  • Run telegraf -config telegraf.conf -test to output one full measurement sample to STDOUT. NOTE: you may want to run as the telegraf user if you are using the linux packages sudo -u telegraf telegraf -config telegraf.conf -test
  • Run telegraf -config telegraf.conf to gather and send metrics to configured outputs.
  • Run telegraf -config telegraf.conf -filter system:swap. to run telegraf with only the system & swap plugins defined in the config.

Telegraf Options

Telegraf has a few options you can configure under the agent section of the config.

  • hostname: The hostname is passed as a tag. By default this will be the value returned by hostname on the machine running Telegraf. You can override that value here.
  • interval: How often to gather metrics. Uses a simple number + unit parser, e.g. "10s" for 10 seconds or "5m" for 5 minutes.
  • debug: Set to true to gather and send metrics to STDOUT as well as InfluxDB.

Plugin Options

There are 5 configuration options that are configurable per plugin:

  • pass: An array of strings that is used to filter metrics generated by the current plugin. Each string in the array is tested as a prefix against metric names and if it matches, the metric is emitted.
  • drop: The inverse of pass, if a metric name matches, it is not emitted.
  • tagpass: (added in 0.1.5) tag names and arrays of strings that are used to filter metrics by the current plugin. Each string in the array is tested as an exact match against the tag name, and if it matches the metric is emitted.
  • tagdrop: (added in 0.1.5) The inverse of tagpass. If a tag matches, the metric is not emitted. This is tested on metrics that have passed the tagpass test.
  • interval: How often to gather this metric. Normal plugins use a single global interval, but if one particular plugin should be run less or more often, you can configure that here.
Plugin Configuration Examples

This is a full working config that will output CPU data to an InfluxDB instance at 192.168.59.103:8086, tagging measurements with dc="denver-1". It will output measurements at a 10s interval and will collect totalcpu & percpu data.

[tags]
    dc = "denver-1"

[agent]
    interval = "10s"

# OUTPUTS
[outputs]
[[outputs.influxdb]]
    url = "http://192.168.59.103:8086" # required.
    database = "telegraf" # required.
    precision = "s"

# PLUGINS
[cpu]
    percpu = true
    totalcpu = true

Below is how to configure tagpass and tagdrop parameters (added in 0.1.5)

# Don't collect CPU data for cpu6 & cpu7
[cpu.tagdrop]
    cpu = [ "cpu6", "cpu7" ]

[disk]
[disk.tagpass]
    # tagpass conditions are OR, not AND.
    # If the (filesystem is ext4 or xfs) OR (the path is /opt or /home)
    # then the metric passes
    fstype = [ "ext4", "xfs" ]
    path = [ "/opt", "/home" ]

Supported Plugins

You can view usage instructions for each plugin by running telegraf -usage <pluginname>.

Telegraf currently has support for collecting metrics from:

  • aerospike
  • apache
  • bcache
  • disque
  • elasticsearch
  • exec (generic JSON-emitting executable plugin)
  • haproxy
  • httpjson (generic JSON-emitting http service plugin)
  • jolokia (remote JMX with JSON over HTTP)
  • kafka_consumer
  • leofs
  • lustre2
  • memcached
  • mongodb
  • mysql
  • nginx
  • phpfpm
  • ping
  • postgresql
  • procstat
  • prometheus
  • puppetagent
  • rabbitmq
  • redis
  • rethinkdb
  • twemproxy
  • zfs
  • zookeeper
  • system
    • cpu
    • mem
    • io
    • net
    • netstat
    • disk
    • swap

Supported Service Plugins

Telegraf can collect metrics via the following services:

  • statsd

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.

Output options

Telegraf also supports specifying multiple output sinks to send data to, configuring each output sink is different, but examples can be found by running telegraf -sample-config.

Supported Outputs

  • influxdb
  • nsq
  • kafka
  • datadog
  • opentsdb
  • amqp (rabbitmq)
  • mqtt
  • librato
  • prometheus
  • amon

Contributing

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

Documentation

Index

Constants

This section is empty.

Variables

This section is empty.

Functions

func PrintOutputConfig added in v0.2.0

func PrintOutputConfig(name string) error

PrintOutputConfig prints the config usage of a single output.

func PrintPluginConfig added in v0.1.7

func PrintPluginConfig(name string) error

PrintPluginConfig prints the config usage of a single plugin.

func PrintSampleConfig

func PrintSampleConfig(pluginFilters []string, outputFilters []string)

PrintSampleConfig prints the sample config

Types

type Accumulator added in v0.2.0

type Accumulator interface {
	Add(measurement string, value interface{},
		tags map[string]string, t ...time.Time)
	AddFields(measurement string, fields map[string]interface{},
		tags map[string]string, t ...time.Time)

	SetDefaultTags(tags map[string]string)
	AddDefaultTag(key, value string)

	Prefix() string
	SetPrefix(prefix string)

	Debug() bool
	SetDebug(enabled bool)
}

func NewAccumulator added in v0.2.0

func NewAccumulator(
	plugin *ConfiguredPlugin,
	points chan *client.Point,
) Accumulator

type Agent

type Agent struct {

	// Interval at which to gather information
	Interval internal.Duration

	// RoundInterval rounds collection interval to 'interval'.
	//     ie, if Interval=10s then always collect on :00, :10, :20, etc.
	RoundInterval bool

	// Interval at which to flush data
	FlushInterval internal.Duration

	// FlushRetries is the number of times to retry each data flush
	FlushRetries int

	// FlushJitter tells
	FlushJitter internal.Duration

	// Option for outputting data in UTC
	UTC bool `toml:"utc"`

	// Precision to write data at
	// Valid values for Precision are n, u, ms, s, m, and h
	Precision string

	// Option for running in debug mode
	Debug    bool
	Hostname string

	Tags map[string]string
	// contains filtered or unexported fields
}

Agent runs telegraf and collects data based on the given config

func NewAgent

func NewAgent(config *Config) (*Agent, error)

NewAgent returns an Agent struct based off the given Config

func (*Agent) Close added in v0.1.4

func (a *Agent) Close() error

Close closes the connection to all configured outputs

func (*Agent) Connect

func (a *Agent) Connect() error

Connect connects to all configured outputs

func (*Agent) LoadOutputs added in v0.1.4

func (a *Agent) LoadOutputs(filters []string, config *Config) ([]string, error)

LoadOutputs loads the agent's outputs

func (*Agent) LoadPlugins

func (a *Agent) LoadPlugins(filters []string, config *Config) ([]string, error)

LoadPlugins loads the agent's plugins

func (*Agent) Run

func (a *Agent) Run(shutdown chan struct{}) error

Run runs the agent daemon, gathering every Interval

func (*Agent) Test

func (a *Agent) Test() error

Test verifies that we can 'Gather' from all plugins with their configured Config struct

type Config

type Config struct {
	// This lives outside the agent because mergeStruct doesn't need to handle
	// maps normally. We just copy the elements manually in ApplyAgent.
	Tags map[string]string
	// contains filtered or unexported fields
}

Config specifies the URL/user/password for the database that telegraf will be logging to, as well as all the plugins that the user has specified

func LoadConfig

func LoadConfig(path string) (*Config, error)

LoadConfig loads the given config file and returns a *Config pointer

func (*Config) ApplyAgent

func (c *Config) ApplyAgent(a *Agent) error

ApplyAgent loads the Agent struct built from the config into the given Agent struct. Overrides only values in the given struct that were set in the config.

func (*Config) ApplyOutput added in v0.1.4

func (c *Config) ApplyOutput(name string, v interface{}) error

ApplyOutput loads the Output struct built from the config into the given Output struct. Overrides only values in the given struct that were set in the config.

func (*Config) GetPluginConfig added in v0.2.2

func (c *Config) GetPluginConfig(name string) *ConfiguredPlugin

func (*Config) ListTags

func (c *Config) ListTags() string

ListTags returns a string of tags specified in the config, line-protocol style

func (*Config) LoadDirectory added in v0.2.0

func (c *Config) LoadDirectory(path string) error

func (*Config) Outputs added in v0.1.4

func (c *Config) Outputs() map[string]outputs.Output

Outputs returns the configured outputs as a map of name -> outputs.Output

func (*Config) OutputsDeclared added in v0.1.4

func (c *Config) OutputsDeclared() map[string]outputs.Output

OutputsDeclared returns the name of all outputs declared in the config.

func (*Config) Plugins

func (c *Config) Plugins() map[string]plugins.Plugin

Plugins returns the configured plugins as a map of name -> plugins.Plugin

func (*Config) PluginsDeclared

func (c *Config) PluginsDeclared() map[string]plugins.Plugin

PluginsDeclared returns the name of all plugins declared in the config.

type ConfiguredPlugin

type ConfiguredPlugin struct {
	Name string

	Drop []string
	Pass []string

	TagDrop []TagFilter
	TagPass []TagFilter

	Interval time.Duration
}

ConfiguredPlugin containing a name, interval, and drop/pass prefix lists Also lists the tags to filter

func (*ConfiguredPlugin) ShouldPass

func (cp *ConfiguredPlugin) ShouldPass(measurement string, tags map[string]string) bool

ShouldPass returns true if the metric should pass, false if should drop

type TagFilter added in v0.1.4

type TagFilter struct {
	Name   string
	Filter []string
}

TagFilter is the name of a tag, and the values on which to filter

Directories

Path Synopsis
Godeps
cmd

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL