What is Telegraf?
It is an agent for collecting, processing, aggregating, and writing metrics. 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 a tool in the Monitoring Tools category of a tech stack.
Telegraf is an open source tool with 7.2K GitHub stars and 2.7K GitHub forks. Here’s a link to Telegraf's open source repository on GitHub
Who uses Telegraf?
17 companies reportedly use Telegraf in their tech stacks, including Zencom, Houghton Mifflin Harcourt, and Operations.
17 developers on StackShare have stated that they use Telegraf.
Why developers like Telegraf?
Here’s a list of reasons why companies and developers use Telegraf
Be the first to leave a pro
Telegraf Alternatives & Comparisons
What are some alternatives to Telegraf?
See all alternatives
StatsD is a front-end proxy for the Graphite/Carbon metrics server, originally written by Etsy's Erik Kastner. StatsD is a network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP and sends aggregates to one or more pluggable backend services (e.g., Graphite).
collectd gathers statistics about the system it is running on and stores this information. Those statistics can then be used to find current performance bottlenecks (i.e. performance analysis) and predict future system load (i.e. capacity planning). Or if you just want pretty graphs of your private server and are fed up with some homegrown solution you're at the right place, too.
Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics.
Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.
A monitoring framework that aims to be simple, malleable, and scalable. Essentially, Sensu takes the results of “check” scripts run across many systems, and if certain conditions are met; passes their information to one or more “handlers”. Checks are used, for example, to determine if a service like Apache is up or down.