Fluentd VS Riemann

Get Started with Fluentd

Currently, there is no cluster-wide logging. Fluentd can be used to have a unified logging layer for the cluster.

Fluentd hasn't been touched for 8 years? Looking at the repo it looks like it's alive and well. https://github.com/fluent/fluentd

Fluentd is an open-source log management and data collection tool. Just like Logstash, Fluentd uses a pipeline-based architecture. This allows it to collect data from various sources and network traffic and forward it to various destinations.

Fluentd is a powerful log management tool that offers organizations the flexibility and scalability required to handle large volumes of log data from a variety of sources and transport it to various destinations. Utilizing a flexible and modular architecture, Fluentd allows users to easily add new input and output plugins to integrate with a wide range of systems and applications. It supports a wide range of data sources and destinations, including databases, message queues, and data stores.

Substation is an affordable alternative to products like Cribl (~10x cost savings) and is easier to manage than similar open-source projects such as Logstash and fluentd. It's been used in production by the security team at Brex for 2+ years and is ready for any scale, even beyond 100,000 events per second!

There are probably too many to chose from. Logstash, Promtail, Vector, Filebeat, FluentD, Logagent and probably many more

To alleviate some of the pain, it’s a good idea to use industry standards and tooling like OpenTelemetry (https://opentelemetry.io). For data collection specific to logs, open-source tools like LogStash and Fluentd are also popular.

Created and maintained by the creators of fluentd, fluentbit is a lightweight, fast, and scalable logging and metrics processor and forwarder. Built specifically for the cloud and containerized environments, it allows users to collect data from any source, enrich it with filters and forward it to the tool of their choice.

This is fine- we do something similar using riemann.

"It can't go into infinite loop" is utterly irrelevant. Over last maybe 15 years I've used a bunch of apps that just used their own programming language (from simple DSL to "just write exactly how the app is supposed to handle data") and literally not a single time has that become a problem.

Metrics are measurements of something about your system. They are numeric values, over an interval of time, usually with associated metadata (e.g., timestamp, name). They can be raw, calculated, or aggregated over a period of time. They can come from a variety of sources like servers or APIs. Metrics are structured by default and can be stored in open source systems like Prometheus and Riemann or in off-the-shelf solutions like Amazon CloudWatch and Azure Monitor. These optimized storage systems allow you to perform queries, create alerts, and store them for long periods of time.

Reason #1 - Riemann https://riemann.io/

Riemann is a tool for distributed system monitoring. It aggregates events from user servers and applications, combines them into a stream and transmits them for further processing or storage. Greater flexibility and fault-tolerance make Riemann different from other similar systems. Moreover, it’s written in Clojure almost completely. The code is available on GitHub and is distributed under Eclipse Public License 1.0.

I did a new release today of Mirabelle, a stream procesing tool heavily inspired by Riemann. I also spent a lot of time on the documentation website if you want to try it, and also wrote an article today about an use case.

Consider dabbling in a project to get your feet wet first. You have a neat problem you want solved? Give it a shot. There an interesting open source project, fork it and tinker with the code. This will be tremendously educational both vocationally and will help you get a feel for if you'd like to work in clojure all the time. There are a lot of projects, but I chose https://github.com/riemann/riemann to read and try better to understand real world clojure.