serilog-sinks-seq VS Elasticsearch

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

You could check out their GitHub and see what is going on https://github.com/elastic/elasticsearch/issues

Link to GitHub -->

I believe the 1024 limit has been upped in recent versions of Elasticsearch

https://github.com/elastic/elasticsearch/issues/92458

Elasticsearch is written in Java and its source code is available on Github.

I don't think the murmur3 hash implementation has changed since it was added as the default in version 2.0 (see the [changes](https://github.com/elastic/elasticsearch/commits/main/server/src/main/java/org/elasticsearch/cluster/routing/Murmur3HashFunction.java)). The plugin itself has seen [more changes](https://github.com/elastic/elasticsearch/commits/main/plugins/mapper-murmur3) but that's IMO because of internals and not visible changes in the calculations.

Mysql is not as open source as postgres (long story). And you can see how open elasticsearch is by just having access to the bugs database https://github.com/elastic/elasticsearch/issue