Alternatives to Telegraf logo

Alternatives to Telegraf

StatsD, collectd, Zabbix, Prometheus, and Sensu are the most popular alternatives and competitors to Telegraf.
210
255
+ 1
16

What is Telegraf and what are its top alternatives?

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 11.7K GitHub stars and 4.9K GitHub forks. Here’s a link to Telegraf's open source repository on GitHub

Top Alternatives to Telegraf

  • StatsD
    StatsD

    It is a network daemon that runs on the Node.js platform and listens for statistics, like counters and timers, sent over UDP or TCP and sends aggregates to one or more pluggable backend services (e.g., Graphite). ...

  • collectd
    collectd

    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
    Zabbix

    Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics. ...

  • Prometheus
    Prometheus

    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. ...

  • Sensu
    Sensu

    Sensu is the future-proof solution for multi-cloud monitoring at scale. The Sensu monitoring event pipeline empowers businesses to automate their monitoring workflows and gain deep visibility into their multi-cloud environments. ...

  • Ganglia
    Ganglia

    It is a scalable distributed monitoring system for high-performance computing systems such as clusters and Grids. It is based on a hierarchical design targeted at federations of clusters. ...

  • Fluentd
    Fluentd

    Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Fluentd helps you unify your logging infrastructure. ...

  • Logstash
    Logstash

    Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching). If you store them in Elasticsearch, you can view and analyze them with Kibana. ...

Telegraf alternatives & related posts

StatsD logo

StatsD

263
276
31
Simple daemon for easy stats aggregation
263
276
+ 1
31
PROS OF STATSD
  • 9
    Open source
  • 7
    Single responsibility
  • 5
    Efficient wire format
  • 3
    Loads of integrations
  • 3
    Handles aggregation
  • 1
    Many implementations
  • 1
    Scales well
  • 1
    Simple to use
  • 1
    NodeJS
CONS OF STATSD
  • 1
    No authentication; cannot be used over Internet

related StatsD posts

Łukasz Korecki
CTO & Co-founder at EnjoyHQ · | 7 upvotes · 270.4K views

We use collectd because of it's low footprint and great capabilities. We use it to monitor our Google Compute Engine machines. More interestingly we setup collectd as StatsD replacement - all our Clojure services push application-level metrics using our own metrics library and collectd pushes them to Stackdriver

See more

A huge part of our continuous deployment practices is to have granular alerting and monitoring across the platform. To do this, we run Sentry on-premise, inside our VPCs, for our event alerting, and we run an awesome observability and monitoring system consisting of StatsD, Graphite and Grafana. We have dashboards using this system to monitor our core subsystems so that we can know the health of any given subsystem at any moment. This system ties into our PagerDuty rotation, as well as alerts from some of our Amazon CloudWatch alarms (we’re looking to migrate all of these to our internal monitoring system soon).

See more
collectd logo

collectd

92
144
5
System and applications metrics collector
92
144
+ 1
5
PROS OF COLLECTD
  • 2
    Open Source
  • 2
    Modular, plugins
  • 1
    KISS
CONS OF COLLECTD
    Be the first to leave a con

    related collectd posts

    Łukasz Korecki
    CTO & Co-founder at EnjoyHQ · | 7 upvotes · 270.4K views

    We use collectd because of it's low footprint and great capabilities. We use it to monitor our Google Compute Engine machines. More interestingly we setup collectd as StatsD replacement - all our Clojure services push application-level metrics using our own metrics library and collectd pushes them to Stackdriver

    See more
    Zabbix logo

    Zabbix

    579
    847
    62
    Track, record, alert and visualize performance and availability of IT resources
    579
    847
    + 1
    62
    PROS OF ZABBIX
    • 18
      Free
    • 9
      Alerts
    • 5
      Service/node/network discovery
    • 4
      Templates
    • 4
      Base metrics from the box
    • 3
      Multi-dashboards
    • 3
      SMS/Email/Messenger alerts
    • 2
      Grafana plugin available
    • 2
      Supports Graphs ans screens
    • 2
      Support proxies (for monitoring remote branches)
    • 1
      Perform website checking (response time, loading, ...)
    • 1
      API available for creating own apps
    • 1
      Templates free available (Zabbix Share)
    • 1
      Works with multiple databases
    • 1
      Advanced integrations
    • 1
      Supports multiple protocols/agents
    • 1
      Complete Logs Report
    • 1
      Open source
    • 1
      Supports large variety of Operating Systems
    • 1
      Supports JMX (Java, Tomcat, Jboss, ...)
    CONS OF ZABBIX
    • 5
      The UI is in PHP
    • 2
      Puppet module is sluggish

    related Zabbix posts

    Shared insights
    on
    DatadogDatadogZabbixZabbixCentreonCentreon

    My team is divided on using Centreon or Zabbix for enterprise monitoring and alert automation. Can someone let us know which one is better? There is one more tool called Datadog that we are using for cloud assets. Of course, Datadog presents us with huge bills. So we want to have a comparative study. Suggestions and advice are welcome. Thanks!

    See more
    Shared insights
    on
    ZabbixZabbixCheckmkCheckmk

    I am looking for an easy to set up and use monitoring solution for my servers and network infrastructure. What are the main differences between Checkmk and Zabbix? What would you recommend and why?

    See more
    Prometheus logo

    Prometheus

    2.8K
    3.3K
    238
    An open-source service monitoring system and time series database, developed by SoundCloud
    2.8K
    3.3K
    + 1
    238
    PROS OF PROMETHEUS
    • 46
      Powerful easy to use monitoring
    • 38
      Flexible query language
    • 32
      Dimensional data model
    • 27
      Alerts
    • 23
      Active and responsive community
    • 22
      Extensive integrations
    • 19
      Easy to setup
    • 12
      Beautiful Model and Query language
    • 7
      Easy to extend
    • 6
      Nice
    • 3
      Written in Go
    • 2
      Good for experimentation
    • 1
      Easy for monitoring
    CONS OF PROMETHEUS
    • 12
      Just for metrics
    • 6
      Bad UI
    • 6
      Needs monitoring to access metrics endpoints
    • 4
      Not easy to configure and use
    • 3
      Supports only active agents
    • 2
      Written in Go
    • 2
      TLS is quite difficult to understand
    • 2
      Requires multiple applications and tools
    • 1
      Single point of failure

    related Prometheus posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 15 upvotes · 3.1M views

    Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

    By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

    To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

    https://eng.uber.com/m3/

    (GitHub : https://github.com/m3db/m3)

    See more
    Matt Menzenski
    Senior Software Engineering Manager at PayIt · | 14 upvotes · 231.8K views

    Grafana and Prometheus together, running on Kubernetes , is a powerful combination. These tools are cloud-native and offer a large community and easy integrations. At PayIt we're using exporting Java application metrics using a Dropwizard metrics exporter, and our Node.js services now use the prom-client npm library to serve metrics.

    See more
    Sensu logo

    Sensu

    199
    235
    55
    Simple. Scalable. Multi-cloud monitoring.
    199
    235
    + 1
    55
    PROS OF SENSU
    • 13
      Support for almost anything
    • 11
      Easy setup
    • 9
      Message routing
    • 7
      Devs can code their own checks
    • 5
      Ease of use
    • 3
      Nagios plugin compatibility
    • 3
      Price
    • 3
      Easy configuration, scales well and performance is good
    • 1
      Written in Go
    CONS OF SENSU
    • 1
      Plugins
    • 1
      Written in Go

    related Sensu posts

    Ganglia logo

    Ganglia

    27
    80
    0
    Scalable distributed monitoring system
    27
    80
    + 1
    0
    PROS OF GANGLIA
      Be the first to leave a pro
      CONS OF GANGLIA
        Be the first to leave a con

        related Ganglia posts

        Fluentd logo

        Fluentd

        519
        623
        36
        Unified logging layer
        519
        623
        + 1
        36
        PROS OF FLUENTD
        • 10
          Open-source
        • 9
          Great for Kubernetes node container log forwarding
        • 9
          Lightweight
        • 8
          Easy
        CONS OF FLUENTD
          Be the first to leave a con

          related Fluentd posts

          Logstash logo

          Logstash

          9.2K
          7.2K
          102
          Collect, Parse, & Enrich Data
          9.2K
          7.2K
          + 1
          102
          PROS OF LOGSTASH
          • 68
            Free
          • 18
            Easy but powerful filtering
          • 12
            Scalable
          • 2
            Kibana provides machine learning based analytics to log
          • 1
            Great to meet GDPR goals
          • 1
            Well Documented
          CONS OF LOGSTASH
          • 4
            Memory-intensive
          • 1
            Documentation difficult to use

          related Logstash posts

          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 5.2M views

          Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

          It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

          I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

          We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

          If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

          The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

          Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

          See more
          Tanya Bragin
          Product Lead, Observability at Elastic · | 10 upvotes · 659.9K views

          ELK Stack (Elasticsearch, Logstash, Kibana) is widely known as the de facto way to centralize logs from operational systems. The assumption is that Elasticsearch (a "search engine") is a good place to put text-based logs for the purposes of free-text search. And indeed, simply searching text-based logs for the word "error" or filtering logs based on a set of a well-known tags is extremely powerful, and is often where most users start.

          See more