influxdata/telegraf

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on September 3rd, 2026
Created on April 1st, 2015
Open Issues & Pull Requests: 409 (+0)
GitHub issues: Enabled
Number of forks: 5,836
Total Stargazers: 17,795 (+0)
Total Subscribers: 299 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Telegraf is a metrics and logs collection agent that gathers data from diverse sources, processes it, and writes it to storage or messaging systems.

The tool solves the problem of unified data collection across heterogeneous infrastructure by offering a plugin-based architecture. Users define a TOML configuration specifying which input plugins to collect from and which output plugins to send to, then Telegraf runs as a standalone agent collecting data at regular intervals. The agent compiles into a single static binary with no external dependencies, simplifying deployment across different environments including servers, containers, and edge devices.

Telegraf suits organizations running complex, multi-vendor infrastructure who need to centralize observability data. The breadth of its plugin ecosystem—covering industrial protocols like OPC UA and Modbus, cloud services, container platforms, messaging systems, and Windows-specific sources—makes it valuable for teams already invested in the InfluxDB ecosystem or those seeking a vendor-neutral collection point. The ability to embed custom code for data transformation and the straightforward TOML configuration reduce friction for teams building data pipelines.

The project maintains active engagement with a substantial user base, with nearly all open issues originating from outside users rather than the core team, indicating real-world adoption at scale. Maintainers typically respond to new issues and pull requests within days. Work in the issue tracker centers on bug reports, feature requests, and follow-ups awaiting user response, reflecting a mature project managing both stability concerns and community-driven feature development.