I am not sure every comment critical of elastic's move has been down voted consistently to grey them out.
This has happened with my comments on other posts, it's content is that instead of using license encumbered ELK product people can use SOLR, Vespa or Lucene which are truly open source. It was down voted enough to move it to last or grey it out to make it difficult to read.
solr, vespa, and lucene only replace the elasticsearch part of ELk. Fluentd is an obvious replacment for Logstash, but I'm not sure what a good open source alternative to Kibana is that is compatible with solr, vespa, or lucene.
Lucene is a low level library which is internally used by ElasticSearch and Solr. Vespa is built from the ground up - it does not use Lucene.
Grafana comes to mind as kibana replacement.
My understanding is that grafana is good at visualization, not searching for specific events.
this is changing as grafana evolves to move into logs in addition to metrics
Interesting, however it doesn't seem like it is a full replacement, since it doesn't do full text indexing:
> Loki is meant to be complementary to existing solutions like Elasticsearch and Splunk that do full text indexing.
As someone who maintains an Elasticsearch plugin, you often have to do A LOT of research into how Elastic themselves have dealt with their undocumented, constantly evolving APIs to figure out how to adapt your own code. Stuff like this happens all the time where some boilerplate code changes, you copy in the way Elastic themselves did it. Given how the code is now a mix of Elastic and Apache code, now you can create a host of legal liability by accidentally taking the wrong piece of boilerplate.
Potential legal liability on top the headaches of maintaining an open source project in my spare time with almost no support. Oh joy.