Here's the blog post describing the system<p><a href="https://peter.bourgon.org/ok-log/" rel="nofollow">https://peter.bourgon.org/ok-log/</a><p>And the original HN post<p><a href="https://news.ycombinator.com/item?id=13418125" rel="nofollow">https://news.ycombinator.com/item?id=13418125</a>
He describes Heka (built by Mozilla) as abandoned. This is true, but we have a re-write in C that is significantly faster and in active development [0].<p>[0] <a href="https://github.com/mozilla-services/hindsight" rel="nofollow">https://github.com/mozilla-services/hindsight</a>
While super-interesting (and something that I wish I had time to really evaluate against Elasticsearch/Solr), I feel like it's missing one of the most useful things about Loggly/ES/Solr - the ability to quickly visualize log trends. And despite the statement that it's a "distributed and coördination-free log management system for big ol' clusters", I'm confused why you would want a "big ol' cluster" without visualization or field searches more complex (and less computationally expensive) than regexes. Am I missing something?<p>e: To be fair, I'm not attempting at all to defend Elasticsearch/Solr, just slightly confused about the actual use cases in prod.
There is actual a fair amount of coordination in this logging system -- with the combination of redirects and gossip to handle them -- but it does seem to be the right kind of coordination.