3 ms·

Elasticsearch is good because it just ingests whatever you sent to it, which allows you to deliver solutions rather quickly. Having said this, I agree there ar

Elasticsearch is good because it just ingests whatever you sent to it, which allows you to deliver solutions rather quickly. Having said this, I agree there are better solutions. (Also, Elasticsearch shines because of its full text search capability, which is not often exploited in case of logs.) Loki is fine (or better said, it will be fine once they finally release a version without write-out-of-order constrain) but I find its lack of high-availability solution a bit frustrating. ClickHouse, on the other side, is just magnificent. I use it in combination with Vector as message pipeline solution (it's an alternative to Fluentd, let's say). So, yes, Elasticsearch is just not great and not only for logs, but for everything else that doesn't require full text search, in my opinion.

wardb 5y ago
Out of Order support is available in Loki's main branch and included in the next release. It's already live in production on Grafana Cloud. https://grafana.com/blog/2021/09/16/avoid-dropped-logs-due-to-out-of-order-timestamps-with-a-new-loki-feature/ https://grafana.com/blog/2021/09/16/avoid-dropped-logs-due-t... High availability in Loki is supported in distributed mode. Helm chart here: https://github.com/grafana/helm-charts/tree/main/charts/loki-distributed https://github.com/grafana/helm-charts/tree/main/charts/loki...
- pachico 5y ago
  Yes, I'll try the next release, that's why I said it wasn't released yet :) Regarding HA, I meant something beyond a k8s deployment.