Alternatives to Filebeat logo

Alternatives to Filebeat

Logstash, Fluentd, Rsyslog, Metricbeat, and Kafka are the most popular alternatives and competitors to Filebeat.
117
231
+ 1
0

What is Filebeat and what are its top alternatives?

It helps you keep the simple things simple by offering a lightweight way to forward and centralize logs and files.
Filebeat is a tool in the Log Management category of a tech stack.

Top Alternatives to Filebeat

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

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

  • Rsyslog
    Rsyslog

    It offers high-performance, great security features and a modular design. It is able to accept inputs from a wide variety of sources, transform them, and output to the results to diverse destinations. ...

  • Metricbeat
    Metricbeat

    Collect metrics from your systems and services. From CPU to memory, Redis to NGINX, and much more, It is a lightweight way to send system and service statistics. ...

  • Kafka
    Kafka

    Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design. ...

  • Logback
    Logback

    It is intended as a successor to the popular log4j project. It is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks and logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. ...

  • SLF4J
    SLF4J

    It is a simple Logging Facade for Java (SLF4J) serves as a simple facade or abstraction for various logging frameworks allowing the end user to plug in the desired logging framework at deployment time. ...

  • Serilog
    Serilog

    It provides diagnostic logging to files, the console, and elsewhere. It is easy to set up, has a clean API, and is portable between recent .NET platforms. ...

Filebeat alternatives & related posts

Logstash logo

Logstash

9.7K
7.3K
102
Collect, Parse, & Enrich Data
9.7K
7.3K
+ 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.3M 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 · 665.4K 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
Fluentd logo

Fluentd

539
632
37
Unified logging layer
539
632
+ 1
37
PROS OF FLUENTD
  • 11
    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

    Rsyslog logo

    Rsyslog

    27
    56
    0
    A high-performance system for log processing
    27
    56
    + 1
    0
    PROS OF RSYSLOG
      Be the first to leave a pro
      CONS OF RSYSLOG
        Be the first to leave a con

        related Rsyslog posts

        Metricbeat logo

        Metricbeat

        46
        109
        2
        A Lightweight Shipper for Metrics
        46
        109
        + 1
        2
        PROS OF METRICBEAT
        • 1
          Simple
        • 1
          Easy to setup
        CONS OF METRICBEAT
          Be the first to leave a con

          related Metricbeat posts

          Sunil Chaudhari

          Hi, We have a situation, where we are using Prometheus to get system metrics from PCF (Pivotal Cloud Foundry) platform. We send that as time-series data to Cortex via a Prometheus server and built a dashboard using Grafana. There is another pipeline where we need to read metrics from a Linux server using Metricbeat, CPU, memory, and Disk. That will be sent to Elasticsearch and Grafana will pull and show the data in a dashboard.

          Is it OK to use Metricbeat for Linux server or can we use Prometheus?

          What is the difference in system metrics sent by Metricbeat and Prometheus node exporters?

          Regards, Sunil.

          See more
          Kafka logo

          Kafka

          18.8K
          17.8K
          596
          Distributed, fault tolerant, high throughput pub-sub messaging system
          18.8K
          17.8K
          + 1
          596
          PROS OF KAFKA
          • 126
            High-throughput
          • 119
            Distributed
          • 90
            Scalable
          • 84
            High-Performance
          • 65
            Durable
          • 37
            Publish-Subscribe
          • 19
            Simple-to-use
          • 17
            Open source
          • 11
            Written in Scala and java. Runs on JVM
          • 8
            Message broker + Streaming system
          • 4
            Avro schema integration
          • 4
            Robust
          • 4
            KSQL
          • 2
            Suport Multiple clients
          • 2
            Partioned, replayable log
          • 1
            Flexible
          • 1
            Extremely good parallelism constructs
          • 1
            Simple publisher / multi-subscriber model
          • 1
            Fun
          CONS OF KAFKA
          • 29
            Non-Java clients are second-class citizens
          • 27
            Needs Zookeeper
          • 7
            Operational difficulties
          • 2
            Terrible Packaging

          related Kafka posts

          Eric Colson
          Chief Algorithms Officer at Stitch Fix · | 21 upvotes · 2.4M views

          The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

          Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

          At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

          For more info:

          #DataScience #DataStack #Data

          See more
          John Kodumal

          As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

          We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

          See more
          Logback logo

          Logback

          1.3K
          58
          0
          A logging framework for Java applications
          1.3K
          58
          + 1
          0
          PROS OF LOGBACK
            Be the first to leave a pro
            CONS OF LOGBACK
              Be the first to leave a con

              related Logback posts

              SLF4J logo

              SLF4J

              1.1K
              53
              0
              Simple logging facade for Java
              1.1K
              53
              + 1
              0
              PROS OF SLF4J
                Be the first to leave a pro
                CONS OF SLF4J
                  Be the first to leave a con

                  related SLF4J posts

                  Serilog logo

                  Serilog

                  1.1K
                  84
                  0
                  A portable and structured logging framework to record diagnostic logs
                  1.1K
                  84
                  + 1
                  0
                  PROS OF SERILOG
                    Be the first to leave a pro
                    CONS OF SERILOG
                      Be the first to leave a con

                      related Serilog posts