Telegraf allows users to specify multiple output sinks in the configuration file.
Supported Telegraf output plugins
The Amazon CloudWatch output plugin send metrics to Amazon CloudWatch.
The Amazon Kinesis output plugin is an experimental plugin that is still in the early stages of development. It will batch up all of the points into one
PUT request to Kinesis. This should save the number of API requests by a considerable level.
If the point value being sent cannot be converted to a float64 value, the metric is skipped.
Metrics are grouped by converting any
_ characters to
. in the Point Name.
Metrics are written to a topic exchange using
tag, defined in configuration file as
RoutingTag, as a routing key.
The Discard output plugin simply drops all metrics that are sent to it. It is only meant to be used for testing purposes.
The File output plugin writes Telegraf metrics to files.
Google Cloud PubSub
The Graylog output plugin writes to a Graylog instance using the
The HTTP output plugin sends metrics in a HTTP message encoded using one of the output data formats. For
data_formats that support batching, metrics are sent in batch format.
The InfluxDB v1.x output plugin writes to InfluxDB using HTTP or UDP.
Instrumental accepts stats in a format very close to Graphite, with the only difference being that the type of stat (gauge, increment) is the first token, separated from the metric itself by whitespace. The increment type is only used if the metric comes in as a counter through [[input.statsd]].
Microsoft Azure Application Insights
The Microsoft Azure Application Insights output plugin writes Telegraf metrics to Application Insights (Microsoft Azure).
Microsoft Azure Monitor
Note: The Azure Monitor custom metrics service is currently in preview and not available in a subset of Azure regions.
The Microsoft Azure Monitor output plugin sends custom metrics to Microsoft Azure Monitor. Azure Monitor has a metric resolution of one minute. To handle this in Telegraf, the Azure Monitor output plugin automatically aggregates metrics into one minute buckets, which are then sent to Azure Monitor on every flush interval.
For a Microsoft blog posting on using Telegraf with Microsoft Azure Monitor, see Collect custom metrics for a Linux VM with the InfluxData Telegraf Agent.
The metrics from each input plugin will be written to a separate Azure Monitor namespace, prefixed with
Telegraf/ by default. The field name for each metric is written as the Azure Monitor metric name. All field values are written as a summarized set that includes
count. Tags are written as a dimension on each Azure Monitor metric.
The NATS Output output plugin writes to a (list of) specified NATS instance(s).
The NSQ output plugin writes to a specified NSQD instance, usually local to the producer. It requires a server name and a topic name.
The OpenTSDB output plugin writes to an OpenTSDB instance using either the telnet or HTTP mode.
Using the HTTP API is the recommended way of writing metrics since OpenTSDB 2.0 To use HTTP mode, set
useHttp to true in config. You can also control how many metrics are sent in each HTTP request by setting
batchSize in config. See http://opentsdb.net/docs/build/html/api_http/put.html for details.
The Stackdriver output plugin writes to the Google Cloud Stackdriver API and requires Google Cloud authentication with Google Cloud using either a service account or user credentials. For details on pricing, see the Stackdriver documentation.
project to specify where Stackdriver metrics will be delivered to.
Metrics are grouped by the
namespace variable and metric key, for example
The Wavefront output plugin writes to a Wavefront proxy, in Wavefront data format over TCP.
Deprecated Telegraf output plugins
The Riemann Legacy output plugin will be deprecated in a future release, see https://github.com/influxdata/telegraf/issues/1878 for more details & discussion.