Different systems expose measurements through different interfaces, and a monitoring pipeline may need to combine several of them. Telegraf is an agent with input plugins for collecting data, processing steps for changing it and output plugins for sending it onward. It can gather from local systems, poll services or consume messages depending on configuration. The selected plugins determine where it should run and how many copies are safe; extra replicas can duplicate collection rather than simply add capacity.
Current guidance
This record identifies InfluxData Telegraf, whose inputs, processors, aggregators and outputs form a configurable telemetry pipeline. InfluxData publishes a Helm chart and documents conversion of chart values into Telegraf’s TOML configuration. The README retains very old minimum-version wording, so verify the rendered resources and selected release against the actual cluster instead of treating that line as a current support matrix.
Node-local collection, central polling and queue consumption have different replica and permission needs. Multiple replicas can duplicate polling or divide messages depending on the input plugin. Review metric types, tags, aggregation intervals and output buffering, and choose the output plugin appropriate to the destination’s protocol and version; Telegraf is not restricted to one generation of InfluxDB.
When migrating, render and inspect the generated TOML, then test representative input records and output measurements. Preserve tag names used by dashboards and alerts, check credentials and TLS, and observe behavior when the destination is unavailable. An agent starting successfully does not establish that every configured plugin loaded or that buffering meets the required data-loss tolerance.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Telegraf is part of the TICK Stack and is a plugin-driven server agent for collecting and reporting metrics. Telegraf has integrations to source a variety of metrics, events, and logs directly from the containers and systems it’s running on, pull metrics from third-party APIs, or even listen for metrics via a StatsD and Kafka consumer services. It also has output plugins to send metrics to a variety of other data stores, services, and message queues, including InfluxDB, Graphite, OpenTSDB, Datadog, Librato, Kafka, MQTT, NSQ, and many others.
Prerequisites
- Kubernetes 1.4+ with Beta APIs enabled
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:
- Input Plugins collect metrics from the system, services, or 3rd party APIs
- Processor Plugins transform, decorate, and/or filter metrics
- Aggregator Plugins create aggregate metrics (e.g. mean, min, max, quantiles, etc.)
- Output Plugins write metrics to various destinations
New plugins are designed to be easy to contribute, we’ll eagerly accept pull requests and will manage the set of plugins that Telegraf supports.
Collect and send all kinds of data
- Databases: Connect to data sources like MongoDB, MySQL, Redis, and others to collect and send metrics.
- Systems: Collect metrics from your modern stack of cloud platforms, containers, and orchestrators.
- IoT Sensors: Collect critical stateful data (pressure levels, temp levels, etc.) from IoT sensors and devices.
Agent
Telegraf is a metric collection daemon that can collect metrics from a wide array of inputs and write them into a wide array of outputs. It is plugin-driven for both collection and output of data so it is easily extendable. It is written in Go, which means that it is a compiled and standalone binary that can be executed on any system with no need for external dependencies, no npm, pip, gem, or other package management tools required.
Coverage
With over 200 plugins already written by subject matter experts on the data in the community, it is easy to start collecting metrics from your end-points. Even better, the ease of plugin development means you can build your own plugin to fit with your monitoring needs. You can even use Telegraf to parse the input data formats into metrics. These include InfluxDB Line Protocol, JSON, Graphite, Value, Nagios, and Collectd.
Flexible
The Telegraf plugin architecture supports your processes and does not force you to change your workflows to work with the technology. Whether you need it to sit on the edge, or in a centralized manner, it just fits with your architecture instead of the other way around. Telegraf’s flexibility makes it an easy decision to implement.
Sources & further reading
Spotted something that needs another look?
Help improve this page →