Telegraf documentation
Telegraf is a plugin-driven server agent for collecting, processing, and writing metrics and events. Written in Go, Telegraf compiles into a single binary with no external dependencies and requires minimal memory.
Telegraf moves data through a configurable pipeline:
- Input plugins collect metrics from systems, services, databases, and IoT sensors.
- Processor plugins transform and filter metrics as they pass through the pipeline.
- Aggregator plugins create aggregate metrics, such as running means, minimums, and maximums, over configurable periods.
- Output plugins write metrics to InfluxDB and other destinations.
To learn how metrics move through the pipeline, see How Telegraf works.
Key capabilities
- 400+ plugins: collect from and write to databases, message queues, cloud services, and IoT devices. Browse the Plugin directory.
- Parsers and serializers: read and write many input and output data formats, including JSON, CSV, Prometheus, and InfluxDB line protocol.
- Metric filtering: select and modify metrics at each stage of the pipeline with metric filtering.
- Buffering and delivery: buffer metrics in memory or on disk and retry failed writes.
- Secret stores: keep credentials out of plain-text configuration files with secret store plugins.
- Manage agents at scale: use Telegraf Controller to centrally manage configurations and monitor Telegraf agents across your infrastructure.
Get started
For an introduction to Telegraf and an overview of how it works, watch the following video:
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for Telegraf and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.