influxdata /telegraf

Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.

★ 17,900⑂ 5,850
GoCreated 2015-04-01influxdata.com/telegraf
17,900
stars
+5+7+49
5,850
forks
–
watchers
–
prs
–
issues
–
releases
–
discussions

README

!tiger Telegraf






Telegraf is an agent for collecting, processing, aggregating, and writing
metrics, logs, and other arbitrary data.

 Offers a comprehensive suite of over 300 plugins, covering a wide range of
  functionalities including system monitoring, cloud services, and message
  passing
 Enables the integration of user-defined code to collect, transform, and
  transmit data efficiently
 Compiles into a standalone static binary without any external dependencies,
  ensuring a streamlined deployment process
 Utilizes TOML for configuration, providing a user-friendly and unambiguous
  setup experience
 Developed with contributions from a diverse community of over 1,200
  contributors

Users can choose plugins from a wide range of topics, including but not limited
to:

 Devices: [OPC UA][], [Modbus][]
 Logs: [File][], [Tail][], [Directory Monitor][]
 Messaging: [AMQP][], [Kafka][], [MQTT][]
 Monitoring: [OpenTelemetry][], [Prometheus][]
 Networking: [Cisco TelemetryMDT][], [gNMI][]
 System monitoring: [CPU][], [Memory][], [Disk][], [Network][], [SMART][],
  [Docker][], [Nvidia SMI][], etc.
 Universal: [Exec][], [HTTP][], [HTTP Listener][], [SNMP][], [SQL][]
 Windows: [Event Log][], [Management Instrumentation][],
  [Performance Counters][]

 🔨 Installation

For binary builds, Docker images, RPM & DEB packages, and other builds of
Telegraf, please see the install guide.

See the releases documentation for details on versioning
and when releases are made.

 💻 Usage

Users define a TOML configuration with the plugins and settings they wish to
use, then pass that configuration to Telegraf. The Telegraf agent then
collects data from inputs at each interval and sends data to outputs at each
flush interval.

For a basic walkthrough see quick start.

 📖 Documentation

For a full list of documentation including tutorials, reference and other
material, start with the /docs directory.

Additionally, each plugin has its own README that includes details about how to
configure, use, and sometimes debug or troubleshoot. Look under the
/plugins directory for specific plugins.

Here are some commonly used documents:

 Changelog
 Configuration
 FAQ
 Releases
 Security

 ❤️ Contribute



We love our community of over 1,200 contributors! Many of the plugins included
in Telegraf were originally contributed by community members. Check out
our contributing guide if you are interested in helping out.
Also, join us on our Community Slack or
Community Forums if you have questions or
comments for our engineering teams.

If you are completely new to Telegraf and InfluxDB, you can also enroll for free
at InfluxDB university to take courses
to learn more.

 ℹ️ Support




Please use the Community Slack or
Community Forums if you have questions or
comments for our engineering teams. GitHub issues are limited to actual issues
and feature requests only.

 📜 License



[OPC UA]: https://github.com/influxdata/telegraf/tree/master/plugins/inputs/opcua
[Modbus]: https://github

Snapshot: 2026-11-10T09:35:25Z · Data license Apache-2.0 · JSON