serilog-sinks-seq VS logs-benchmark

I dont know why you want to use Graylog, but just fyi maybe https://datalust.co/seq is a alternative.

You could use something like Seq to stream all the logs back to you.

Valuable related discussion: https://www.reddit.com/r/devops/comments/13ab0l5/lightweight...

Highlights:

* Grafana and Loki seems to be favorite

* https://datalust.co/seq is the easiest to deploy (single container)

* https://github.com/tstack/lnav CLI based tool

https://datalust.co/seq (my employer) uses a custom database built with Rust. We are about to remove the last C# database code because, as the previous commenter noted, garbage collection and databases don't mix.

Over the next few years I expect we will see a lot of new databases written in Rust.

https://blog.datalust.co/what-will-seq-vnext-look-like-on-th...

I know I’m a little late to the game, but check out Seq. If you use Docker, you can deploy Seq and Seq-input-gelf Docker containers, set gelf as the default logging driver in your daemon.json, and point it at you Seq instance. That’s pretty much it. Seq also accepts a bunch of other log inputs, like Greylog, for things that don’t run in Docker.

There are several popular logging servers that store and process structured log data. The ones I currently know are SigNoz, Seq, New Relic and Kibana. The latter is, in a nutshell, a user interface to visualize Elasticsearch data.

Another for Seq.

Seq for centralized logging in both development and production environments https://datalust.co/seq

Seq has a free option for individuals - https://datalust.co/seq

I am a maintainer at SigNoz. Nice to see OpenObserve's belief that the future of Observability should be OpenSource. We chose clickhouse rather than building a database as it takes multi-year effort to move a db to maturity and clickhouse has been battle-tested at Yandex, Uber and Cloudflare. Clickhouse also provides native integration with s3 and other blob storages. Our users have been using disk as hot storage for a week and moving the data to s3 after that. Tiered storage is really cool in terms of query performance.

We have also seen logs data of our users at a compression ratio of 30x/40x. We have published a logs benchmark (https://github.com/SigNoz/logs-benchmark) where the data is very high-cardinal (causing a compression factor of only 2.5x). Would love to see how does OpenObserve perform in that dataset someday.

Wishing you best for the journey ahead.

Did you update the benchmark after you got feedback from this user at Hacker News or after you got the feedback that including Loki here is kinda pointless?