Alternatives to Fluentd logo

Alternatives to Fluentd

Logstash, Splunk, collectd, Filebeat, and Elasticsearch are the most popular alternatives and competitors to Fluentd.
231
146
+ 1
4

What is Fluentd and what are its top alternatives?

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.
Fluentd is a tool in the Log Management category of a tech stack.
Fluentd is an open source tool with 8.5K GitHub stars and 1K GitHub forks. Here鈥檚 a link to Fluentd's open source repository on GitHub

Fluentd alternatives & related posts

Logstash logo

Logstash

2.8K
1.9K
95
2.8K
1.9K
+ 1
95
Collect, Parse, & Enrich Data
Logstash logo
Logstash
VS
Fluentd logo
Fluentd

related Logstash posts

Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD | 13 upvotes 283.6K views
Amazon EC2
Amazon EC2
LXC
LXC
CircleCI
CircleCI
Docker
Docker
Git
Git
Vault
Vault
Apache Maven
Apache Maven
Slack
Slack
Jenkins
Jenkins
TeamCity
TeamCity
Logstash
Logstash
Kibana
Kibana
Elasticsearch
Elasticsearch
Ansible
Ansible
VirtualBox
VirtualBox
Vagrant
Vagrant

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
Tanya Bragin
Product Lead, Observability at Elastic | 10 upvotes 68K views
atElasticElastic
Kibana
Kibana
Logstash
Logstash
Elasticsearch
Elasticsearch

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
Splunk logo

Splunk

153
84
0
153
84
+ 1
0
Search, monitor, analyze and visualize machine data
    Be the first to leave a pro
    Splunk logo
    Splunk
    VS
    Fluentd logo
    Fluentd

    related Splunk posts

    Grafana
    Grafana
    Splunk
    Splunk
    Kibana
    Kibana

    I use Kibana because it ships with the ELK stack. I don't find it as powerful as Splunk however it is light years above grepping through log files. We previously used Grafana but found it to be annoying to maintain a separate tool outside of the ELK stack. We were able to get everything we needed from Kibana.

    See more
    collectd logo

    collectd

    52
    45
    3
    52
    45
    + 1
    3
    System and applications metrics collector
    collectd logo
    collectd
    VS
    Fluentd logo
    Fluentd

    related collectd posts

    艁ukasz Korecki
    艁ukasz Korecki
    CTO & Co-founder at EnjoyHQ | 6 upvotes 53.8K views
    atEnjoyHQEnjoyHQ
    Stackdriver
    Stackdriver
    Clojure
    Clojure
    StatsD
    StatsD
    Google Compute Engine
    Google Compute Engine
    collectd
    collectd

    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
    Filebeat logo

    Filebeat

    30
    15
    0
    30
    15
    + 1
    0
    A lightweight shipper for forwarding and centralizing log data
      Be the first to leave a pro
      Filebeat logo
      Filebeat
      VS
      Fluentd logo
      Fluentd

      related Elasticsearch posts

      Julien DeFrance
      Julien DeFrance
      Principal Software Engineer at Tophatter | 16 upvotes 395.4K views
      atSmartZipSmartZip
      Amazon DynamoDB
      Amazon DynamoDB
      Ruby
      Ruby
      Node.js
      Node.js
      AWS Lambda
      AWS Lambda
      New Relic
      New Relic
      Amazon Elasticsearch Service
      Amazon Elasticsearch Service
      Elasticsearch
      Elasticsearch
      Superset
      Superset
      Amazon Quicksight
      Amazon Quicksight
      Amazon Redshift
      Amazon Redshift
      Zapier
      Zapier
      Segment
      Segment
      Amazon CloudFront
      Amazon CloudFront
      Memcached
      Memcached
      Amazon ElastiCache
      Amazon ElastiCache
      Amazon RDS for Aurora
      Amazon RDS for Aurora
      MySQL
      MySQL
      Amazon RDS
      Amazon RDS
      Amazon S3
      Amazon S3
      Docker
      Docker
      Capistrano
      Capistrano
      AWS Elastic Beanstalk
      AWS Elastic Beanstalk
      Rails API
      Rails API
      Rails
      Rails
      Algolia
      Algolia

      Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

      I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

      For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

      Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

      Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

      Future improvements / technology decisions included:

      Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

      As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

      One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

      See more
      Tim Specht
      Tim Specht
      鈥嶤o-Founder and CTO at Dubsmash | 16 upvotes 76.3K views
      atDubsmashDubsmash
      Memcached
      Memcached
      Algolia
      Algolia
      Elasticsearch
      Elasticsearch
      #SearchAsAService

      Although we were using Elasticsearch in the beginning to power our in-app search, we moved this part of our processing over to Algolia a couple of months ago; this has proven to be a fantastic choice, letting us build search-related features with more confidence and speed.

      Elasticsearch is only used for searching in internal tooling nowadays; hosting and running it reliably has been a task that took up too much time for us in the past and fine-tuning the results to reach a great user-experience was also never an easy task for us. With Algolia we can flexibly change ranking methods on the fly and can instead focus our time on fine-tuning the experience within our app.

      Memcached is used in front of most of the API endpoints to cache responses in order to speed up response times and reduce server-costs on our side.

      #SearchAsAService

      See more
      Prometheus logo

      Prometheus

      963
      692
      183
      963
      692
      + 1
      183
      An open-source service monitoring system and time series database, developed by SoundCloud
      Prometheus logo
      Prometheus
      VS
      Fluentd logo
      Fluentd

      related Prometheus posts

      Conor Myhrvold
      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber | 10 upvotes 561.8K views
      atUber TechnologiesUber Technologies
      Nagios
      Nagios
      Grafana
      Grafana
      Graphite
      Graphite
      Prometheus
      Prometheus

      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鈥檚 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鈥檚 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
      Raja Subramaniam Mahali
      Raja Subramaniam Mahali
      Sysdig
      Sysdig
      Kubernetes
      Kubernetes
      Prometheus
      Prometheus

      We have Prometheus as a monitoring engine as a part of our stack which contains Kubernetes cluster, container images and other open source tools. Also, I am aware that Sysdig can be integrated with Prometheus but I really wanted to know whether Sysdig or sysdig+prometheus will make better monitoring solution.

      See more

      related Papertrail posts

      Sumo Logic
      Sumo Logic
      Papertrail
      Papertrail
      Timber.io
      Timber.io
      LogDNA
      LogDNA
      Logentries
      Logentries
      #Heroku

      Logentries, LogDNA, Timber.io, Papertrail and Sumo Logic provide free pricing plan for #Heroku application. You can add these applications as add-ons very easily.

      See more
      Logentries logo

      Logentries

      267
      117
      102
      267
      117
      + 1
      102
      Real-time log management and analytics built for the cloud
      Logentries logo
      Logentries
      VS
      Fluentd logo
      Fluentd

      related Logentries posts

      Sumo Logic
      Sumo Logic
      Papertrail
      Papertrail
      Timber.io
      Timber.io
      LogDNA
      LogDNA
      Logentries
      Logentries
      #Heroku

      Logentries, LogDNA, Timber.io, Papertrail and Sumo Logic provide free pricing plan for #Heroku application. You can add these applications as add-ons very easily.

      See more
      ELK logo

      ELK

      203
      105
      0
      203
      105
      + 1
      0
      The acronym for three open source projects: Elasticsearch, Logstash, and Kibana
        Be the first to leave a pro
        ELK logo
        ELK
        VS
        Fluentd logo
        Fluentd

        related ELK posts

        Wallace Alves
        Wallace Alves
        Cyber Security Analyst | 1 upvotes 27.3K views
        nginx
        nginx
        Logstash
        Logstash
        Kibana
        Kibana
        Elasticsearch
        Elasticsearch
        ELK
        ELK
        Portainer
        Portainer
        Docker Compose
        Docker Compose
        Docker
        Docker

        Docker Docker Compose Portainer ELK Elasticsearch Kibana Logstash nginx

        See more
        Sumo Logic logo

        Sumo Logic

        134
        83
        19
        134
        83
        + 1
        19
        Cloud Log Management for Application Logs and IT Log Data
        Sumo Logic logo
        Sumo Logic
        VS
        Fluentd logo
        Fluentd

        related Sumo Logic posts

        Sumo Logic
        Sumo Logic
        Papertrail
        Papertrail
        Timber.io
        Timber.io
        LogDNA
        LogDNA
        Logentries
        Logentries
        #Heroku

        Logentries, LogDNA, Timber.io, Papertrail and Sumo Logic provide free pricing plan for #Heroku application. You can add these applications as add-ons very easily.

        See more
        AWS CloudTrail logo

        AWS CloudTrail

        127
        80
        14
        127
        80
        + 1
        14
        Record AWS API calls for your account and have log files delivered to you
        AWS CloudTrail logo
        AWS CloudTrail
        VS
        Fluentd logo
        Fluentd
        Splunk Cloud logo

        Splunk Cloud

        70
        81
        10
        70
        81
        + 1
        10
        Easy and fast way to analyze valuable machine data with the convenience of software as a service (SaaS)
        Splunk Cloud logo
        Splunk Cloud
        VS
        Fluentd logo
        Fluentd

        related LogDNA posts

        Sumo Logic
        Sumo Logic
        Papertrail
        Papertrail
        Timber.io
        Timber.io
        LogDNA
        LogDNA
        Logentries
        Logentries
        #Heroku

        Logentries, LogDNA, Timber.io, Papertrail and Sumo Logic provide free pricing plan for #Heroku application. You can add these applications as add-ons very easily.

        See more
        logz.io logo

        logz.io

        26
        3
        0
        26
        3
        + 1
        0
        A log management and log analysis service
          Be the first to leave a pro
          logz.io logo
          logz.io
          VS
          Fluentd logo
          Fluentd
          Scalyr logo

          Scalyr

          25
          21
          9
          25
          21
          + 1
          9
          Cloud-based log aggregation, server monitoring, and real-time analysis tool.
          Scalyr logo
          Scalyr
          VS
          Fluentd logo
          Fluentd
          SLF4J logo

          SLF4J

          18
          7
          0
          18
          7
          + 1
          0
          Simple logging facade for Java
            Be the first to leave a pro
            SLF4J logo
            SLF4J
            VS
            Fluentd logo
            Fluentd
            Apache Flume logo

            Apache Flume

            15
            8
            0
            15
            8
            + 1
            0
            A service for collecting, aggregating, and moving large amounts of log data
              Be the first to leave a pro
              Apache Flume logo
              Apache Flume
              VS
              Fluentd logo
              Fluentd