Telegraf input plugins are used with the InfluxData time series platform to collect metrics from the system, services, or third party APIs. All metrics are gathered from the inputs you enable and configure in the configuration file.
Note: Telegraf plugins added in the current release are noted with
-- NEW in v1.8. The Release Notes/Changelog has a list of new plugins and updates for other plugins. See the plugin README files for more details.
View usage instructions for each service input by running
telegraf --usage <service-input-name>.
Supported Telegraf input plugins
activemq) – NEW in v.1.8
The ActiveMQ (
activemq) input plugin gathers queues, topics, and subscriber metrics using the ActiveMQ Console API.
The Aerospike (
aerospike) input plugin queries Aerospike servers and gets node statistics and statistics for all configured namespaces.
The Amazon CloudWatch Statistics (
cloudwatch) input plugin pulls metric statistics from Amazon CloudWatch.
The AMQP Consumer (
amqp_consumer) input plugin provides a consumer for use with AMQP 0-9-1, a prominent implementation of this protocol
The Apache HTTP Server (
apache) input plugin collects server performance information using the
mod_status module of the Apache HTTP Server.
mod_status module is configured to expose a page at the
/server-status?auto location of the Apache
server. The ExtendedStatus option must be enabled in order
to collect all available fields. For information about how to configure your server reference the
The Apache Kafka Consumer (
kafka_consumer) input plugin polls a specified Kafka topic and adds messages to InfluxDB.
Messages are expected in the line protocol format.
Consumer Group is used to talk to the Kafka cluster so
multiple instances of Telegraf can read from the same topic in parallel.
The Apache Solr (
solr) input plugin collects stats using the MBean Request Handler.
The Apache Tomcat (
tomcat) input plugin collects statistics available from the Apache Tomcat manager status page (
XML=true returns XML data).
See the Apache Tomcat documentation for details on these statistics.
The Bcache (
bcache) input plugin gets bcache statistics from the
stats_total directory and
beanstalkd) – NEW in v.1.8
The Beanstalkd (
beanstalkd) input plugin collects server stats as well as tube stats (reported by
stats-tube commands respectively).
The Bond (
bond) input plugin collects network bond interface status, bond’s slaves interfaces status and failures count of
bond’s slaves interfaces. The plugin collects these metrics from
The Ceph Storage (
ceph) input plugin collects performance metrics from the MON and OSD nodes in a Ceph storage cluster.
The CGroup (
cgroup) input plugin captures specific statistics per cgroup.
The Chrony (
chrony) input plugin gets standard chrony metrics, requires chronyc executable.
The Conntrack (
conntrack) input plugin collects stats from Netfilter’s conntrack-tools.
The conntrack-tools provide a mechanism for tracking various aspects of network connections as they are processed by
netfilter. At runtime, conntrack exposes many of those connection statistics within
/proc/sys/net. Depending on your
kernel version, these files can be found in either
/proc/sys/net/netfilter and will be
prefixed with either
nf_. This plugin reads the files specified in its configuration and publishes each one as
a field, with the prefix normalized to
The Consul (
consul) input plugin will collect statistics about all health checks registered in the Consul.
It uses Consul API to query the data.
It will not report the telemetry but Consul can report those stats already using StatsD protocol, if needed.
The Couchbase (
couchbase) input plugin reads per-node and per-bucket metrics from Couchbase.
The CouchDB (
couchdb) input plugin gathers metrics of CouchDB using
The CPU (
cpu) input plugin gathers metrics about cpu usage.
The Disk (
disk) input plugin gathers metrics about disk usage by mount point.
The DiskIO (
diskio) input plugin gathers metrics about disk IO by device.
The DMCache (
dmcache) input plugin provides a native collection for dmsetup-based statistics for dm-cache.
The Docker (
docker) input plugin uses the Docker Engine API to gather metrics on running Docker containers. The Docker plugin
uses the Official Docker Client to gather stats from the
Engine API library documentation.
The Exec (
exec) input plugin parses supported Telegraf input data formats (InfluxDB Line Protocol, JSON, Graphite, Value, Nagios, Collectd, and Dropwizard into metrics. Each Telegraf metric includes the measurement name, tags, fields, and timesamp.
The Fibaro (
fibaro) input plugin makes HTTP calls to the Fibaro controller API to gather values of hooked devices. Those values could be true (
1) or false (
0) for switches, percentage for dimmers, temperature, etc.
file) – NEW in v.1.8
The File (
file) input plugin updates a list of files every interval and parses the contents using the selected input data format.
Files will always be read in their entirety, if you wish to tail/follow a file use the tail input plugin instead.
filecount) – NEW in v.1.8
The Filecount (
filecount) input plugin counts files in directories that match certain criteria.
The Filestat (
filestat) input plugin gathers metrics about file existence, size, and other stats.
The Fluentd (
fluentd) input plugin gathers metrics from plugin endpoint provided by in_monitor plugin. This plugin understands
data provided by
/api/plugin.json resource (
/api/config.json is not covered).
The Graylog (
graylog) input plugin can collect data from remote Graylog service URLs. This plugin currently supports two
types of endpoints:
- multiple (e.g.,
- namespace (e.g.,
The HAproxy (
haproxy) input plugin gathers metrics directly from any running HAproxy instance. It can do so by using CSV
generated by HAproxy status page or from admin sockets.
The Hddtemp (
hddtemp) input plugin reads data from
The HTTP (
http) input plugin collects metrics from one or more HTTP (or HTTPS) endpoints. The endpoint should have metrics formatted in one of the supported input data formats. Each data format has its own unique set of configuration options which can be added to the input configuration.
The HTTP Listener (
http_listener) input plugin listens for messages sent via HTTP POST. Messages are expected in the InfluxDB
Line Protocol input data format ONLY (other Telegraf input data formats are not supported).
This plugin allows Telegraf to serve as a proxy or router for the
/write endpoint of the InfluxDB HTTP API.
The HTTP Response (
http_response) input plugin gathers metrics for HTTP responses. The measurements and fields include
result_type. Tags for measurements include
icinga2) – NEW in v.1.8
The InfluxDB v1.x (
influxdb) gathers metrics from the exposed InfluxDB v1.x
/debug/vars endpoint. Using Telegraf to extract these metrics to create a “monitor of monitors” is a best practice and allows you to reduce the overhead associated with
capturing and storing these metrics locally within the
_internal database for production deployments.
Read more about this approach here.
The Interrupts (
interrupts) input plugin gathers metrics about IRQs, including
The IPMI Sensor (
ipmi_sensor) input plugin queries the local machine or remote host sensor statistics using the
The Ipset (
ipset) input plugin gathers packets and bytes counters from Linux
ipset. It uses the output of the command
ipset save. Ipsets created without the
counters option are ignored.
The IPtables (
iptables) input plugin gathers packets and bytes counters for rules within a set of table and chain from the Linux’s iptables firewall.
The JTI OpenConfig Telemetry (
jti_openconfig_telemetry) input plugin reads Juniper Networks implementation of OpenConfig telemetry data from listed sensors using the Junos Telemetry Interface. Refer to
openconfig.net for more details about OpenConfig and Junos Telemetry Interface (JTI).
The Kapacitor (
kapacitor) input plugin will collect metrics from the given Kapacitor instances.
The Kernel (
kernel) input plugin gathers kernel statistics from
The Kernel VMStat input plugin gathers kernel statistics from
kibana) – NEW in v.1.8
The Kibana (
kibana) input plugin queries the Kibana status API to obtain the health status of Kibana and some useful metrics.
Note: The Kubernetes input plugin is experimental and may cause high cardinality issues with moderate to large Kubernetes deployments.
The Kubernetes (
kubernetes) input plugin talks to the kubelet API using the
/stats/summary endpoint to gather metrics about the running pods
and containers for a single host. It is assumed that this plugin is running as part of a daemonset within a
Kubernetes installation. This means that Telegraf is running on every node within the cluster. Therefore, you
should configure this plugin to talk to its locally running kubelet.
The Linux Sysctl FS input plugin provides Linux system level file (
sysctl fs) metrics. The documentation on these fields can be found at https://www.kernel.org/doc/Documentation/sysctl/fs.txt.
The Logparser (
logparser) input plugin streams and parses the given log files. Currently, it has the capability of parsing “grok” patterns
from log files, which also supports regular expression (regex) patterns.
Lustre Jobstats allows for RPCs to be tagged with a value, such as a job’s ID. This allows for per job statistics.
The Lustre2 (
lustre2) input plugin collects statistics and tags the data with the
The Mailchimp (
mailchimp) input plugin gathers metrics from the
/3.0/reports MailChimp API.
The Mcrouter (
mcrouter) input plugin gathers statistics data from a mcrouter instance. Mcrouter is a memcached protocol router, developed and maintained by Facebook, for scaling memcached (http://memcached.org/) deployments. It’s a core component of cache infrastructure at Facebook and Instagram where mcrouter handles almost 5 billion requests per second at peak.
The Memcached (
memcached) input plugin gathers statistics data from a Memcached server.
The Microsoft SQL Server (
sqlserver) input plugin provides metrics for your Microsoft SQL Server instance. It currently works with SQL Server
versions 2008+. Recorded metrics are lightweight and use Dynamic Management Views supplied by SQL Server.
The Minecraft (
minecraft) input plugin uses the RCON protocol to collect statistics from a scoreboard on a Minecraft server.
The MongoDB (
mongodb) input plugin collects MongoDB stats exposed by
serverStatus and few more and create a single
measurement containing values.
The MySQL (
mysql) input plugin gathers the statistics data from MySQL servers.
The NATS Consumer (
nats_consumer) input plugin reads from specified NATS subjects and adds messages to InfluxDB. Messages are expected in the Telegraf input data formats. A Queue Group is used when subscribing to subjects so multiple instances of Telegraf can read from a NATS cluster in parallel.
The Net (
net) input plugin gathers metrics about network interface usage (Linux only).
The Netstat (
netstat) input plugin gathers TCP metrics such as established, time-wait and sockets counts by using
The Network Response (
net_response) input plugin tests UDP and TCP connection response time. It can also check response text.
The NGINX (nginx) input plugin reads NGINX basic status information (
The NGINX Plus (
nginx_plus) input plugin is for NGINX Plus, the commercial version of the open source web server NGINX. To use this plugin you will need a license.
For more information, see What’s the Difference between Open Source NGINX and NGINX Plus?.
Structures for NGINX Plus have been built based on history of status module documentation.
The NSQ Consumer (
nsq_consumer) input plugin polls a specified NSQD topic and adds messages to InfluxDB. This plugin allows a message to be in any of the supported data_format types.
The Nstat (
nstat) input plugin collects network metrics from
The NTPq (
ntpq) input plugin gets standard NTP query metrics, requires ntpq executable.
The OpenLDAP (
openldap) input plugin gathers metrics from OpenLDAP’s
The PF (
pf) input plugin gathers information from the FreeBSD/OpenBSD pf firewall. Currently it can retrive information about
the state table: the number of current entries in the table, and counters for the number of searches, inserts, and
removals to the table. The pf plugin retrieves this information by invoking the
pgbouncer) – NEW in v.1.8
The Phfusion 0Passenger (
passenger) input plugin gets Phusion Passenger statistics using their command line utility
The PHP FPM (
phpfpm) input plugin gets phpfpm statistics using either HTTP status page or fpm socket.
The Ping (
ping) input plugin measures the round-trip for ping commands, response time, and other packet statistics.
The Postfix (
postfix) input plugin reports metrics on the postfix queues. For each of the active, hold, incoming, maildrop, and
deferred queues, it will report the queue length (number of items),
size (bytes used by items), and age (age of oldest item in seconds).
The PostgreSQL (
postgresql) input plugin provides metrics for your PostgreSQL database. It currently works with PostgreSQL versions 8.1+.
It uses data from the built in
pg_stat_bgwriter views. The metrics recorded depend on your
version of postgres.
This PostgreSQL Extensible (
postgresql_extensible) input plugin provides metrics for your Postgres database. It has been designed to parse SQL queries in the plugin section of
The PowerDNS (
powerdns) input plugin gathers metrics about PowerDNS using UNIX sockets.
The Processes (
processes) input plugin
gathers info about the total number of processes and groups them by status (zombie, sleeping, running, etc.). On Linux, this plugin requires access to
/proc); on other operating systems, it requires access to execute
The Procstat (
procstat) input plugin can be used to monitor system resource usage by an individual process using their
Processes can be specified either by
pid file, by executable name, by command line pattern matching, by username,
by systemd unit name, or by cgroup name/path (in this order or priority). This plugin uses
pgrep when an executable
name is provided to obtain the
pid. The Procstat plugin transmits IO, memory, cpu, file descriptor-related
measurements for every process specified. A prefix can be set to isolate individual process specific measurements.
The Procstat input plugin will tag processes according to how they are specified in the configuration. If a pid file is used, a “pidfile” tag will be generated. On the other hand, if an executable is used an “exe” tag will be generated.
The Prometheus Format (
prometheus) input plugin input plugin gathers metrics from HTTP servers exposing metrics in Prometheus format.
The Puppet Agent (
puppetagent) input plugin collects variables outputted from the
last_run_summary.yaml file usually
/var/lib/puppet/state/ Puppet Agent Runs. For more information, see Puppet Monitoring: How to Monitor the Success or Failure of Puppet Runs
The Redis (
redis) input plugin gathers the results of the INFO Redis command. There are two separate measurements:
redis_keyspace, the latter is used for gathering database-related statistics.
Additionally the plugin also calculates the hit/miss ratio (
keyspace_hitrate) and the elapsed time since the last RDB
The RethinkDB (
rethinkdb) input plugin works with RethinkDB 2.3.5+ databases that requires username, password authorization,
and Handshake protocol v1.0.
The Riak (
riak) input plugin gathers metrics from one or more Riak instances.
The Salesforce (
salesforce) input plugin gathers metrics about the limits in your Salesforce organization and the remaining usage.
It fetches its data from the limits endpoint of the Salesforce REST API.
The Sensors (
sensors) input plugin collects collects sensor metrics with the sensors executable from the
The SMART (
smart) input plugin gets metrics using the command line utility
smartctl for SMART (Self-Monitoring, Analysis
and Reporting Technology) storage devices. SMART is a monitoring system included in computer hard disk drives (HDDs)
and solid-state drives (SSDs), which include most modern ATA/SATA, SCSI/SAS and NVMe disks. The plugin detects and
reports on various indicators of drive reliability, with the intent of enabling the anticipation of hardware failures.
The SNMP (
snmp) input plugin gathers metrics from SNMP agents.
The StatsD (
statsd) input plugin is a special type of plugin which runs a backgrounded
statsd listener service while Telegraf is running.
StatsD messages are formatted as described in the original etsy statsd implementation.
The System (
system) input plugin gathers general stats on system load, uptime, and number of users logged in. It is basically equivalent to the UNIX
The Tail (
tail) input plugin “tails” a log file and parses each log message.
The Teamspeak 3 (
teamspeak) input plugin uses the Teamspeak 3 ServerQuery interface of the Teamspeak server to collect statistics of one or more virtual servers.
The Telegraf v1.x (
internal) input plugin collects metrics about the Telegraf v1.x agent itself.
Note that some metrics are aggregates across all instances of one type of plugin.
temp) input plugin – NEW in v.1.8
The Temp (
temp) input plugin collects temperature data from sensors.
Tengine Web Server (
tengine) input plugin – NEW in v.1.8
The Trig (
trig) input plugin inserts sine and cosine waves for demonstration purposes.
The Twemproxy (
twemproxy) input plugin gathers data from Twemproxy instances, processes Twemproxy server statistics, processes pool data. and processes backend server (Redis/Memcached) statistics.
VMware vSphere (
vsphere) – NEW in v.1.8
The VMware vSphere (
vsphere) input plugin uses the vSphere API to gather metrics from multiple vCenter servers (clusters, hosts, VMs, and data stores). For more information on the available performance metrics, see Common vSphere Performance Metrics.
The Webhooks (
webhooks) input plugin starts an HTTPS server and registers multiple webhook listeners.
Add new webhooks
If you need a webhook that is not supported, consider adding a new webhook.
The way the Windows Performance Counters (
win_perf_counters) input plugin works is that on load of Telegraf, the plugin will be handed configuration
from Telegraf. This configuration is parsed and then tested for validity such as if the Object, Instance and Counter
existing. If it does not match at startup, it will not be fetched. Exceptions to this are in cases where you query for
all instances “”. By default the plugin does not return
_Total when it is querying for all () as this is redundant.
The Windows Services (
win_services) input plugin reports Windows services info.
X.509 Certificate (
x509_cert) – NEW in v.1.8
The X.509 Certificate (
x509_cert) input plugin provides information about X.509 certificate accessible using the local file or network connection.
The ZFS (
zfs) input plugin provides metrics from your ZFS filesystems. It supports ZFS on Linux and FreeBSD.
It gets ZFS statistics from
/proc/spl/kstat/zfs on Linux and from
zpool on FreeBSD.
The Zipkin (
zipkin) input plugin implements the Zipkin HTTP server to gather trace and timing data needed to troubleshoot latency problems in microservice architectures.
Note: This plugin is experimental. Its data schema may be subject to change based on its main usage cases and the evolution of the OpenTracing standard.
Deprecated Telegraf input plugins
DEPRECATED as of version 1.7. The Cassandra (
cassandra) input plugin collects Cassandra 3 / JVM metrics exposed as MBean attributes through the jolokia REST endpoint. All metrics are collected for each server configured.
DEPRECATED as of version 1.6; use the HTTP (
http) input plugin.
The HTTP JSON (
httpjson) input plugin collects data from HTTP URLs which respond with JSON.
It flattens the JSON and finds all numeric values, treating them as floats.
DEPRECATED as of version 1.5; use the Jolokia2 (
jolokia2) input plugin.
The SNMP Legacy input plugin gathers metrics from SNMP agents.
DEPRECATED as of version 1.3; use the Socket Listener (
socket_listener) input plugin.