Indexing one petabyte of logs per day with Quickwit

Re:Indexing one petabyte of logs per day with Quickwit by tecleandor on Saturday March 23, 2024 @08:09AM (#39799327)

Ah Loki, I wanted to try it at my homelab bit it wasn't as simple as it says. Now I wanted to try Zincsearch or Openobserve. Have you tried that?

[ Parent | on HN ]

Re:Indexing one petabyte of logs per day with Quickwit by netingle on Saturday March 23, 2024 @08:48AM (#39799560)

> it wasn't as simple as it says

mind elaborating? we built loki for some pretty massive scale but I've always tried to make it work at super small scale to. what went wrong?

[ Parent | on HN ]

Re:Indexing one petabyte of logs per day with Quickwit by pranay01 on Saturday March 23, 2024 @09:07AM (#39799653)

You might want to have a look at SigNoz [1] as well. We have also published some perf benchmark wrt Elastic & Loki [2] and have some cool features like logs pipeline for manipulating logs before ingestion

[1] https://github.com/signoz/signoz [2] https://signoz.io/blog/logs-performance-benchmark/

[ Parent | on HN ]

Re:Indexing one petabyte of logs per day with Quickwit by bbkane on Saturday March 23, 2024 @11:48AM (#39800761)

I use OpenObserve and I quite enjoy it

[ Parent | on HN ]

Re:Indexing one petabyte of logs per day with Quickwit by mdaniel on Saturday March 23, 2024 @12:44PM (#39801218)

in case it matters to others, https://github.com/openobserve/openobserve/tree/v0.7.0 is the last Apache2 licensed copy before they went AGPL with 0.7.1

https://github.com/openobserve/openobserve/blob/v0.7.0/.env.... is some "onoz" for me, but just recently someone submitted https://github.com/aenix-io/etcd-operator to the CNCF sandbox so maybe things have gotten better around keeping that PoS alive

[ Parent | on HN ]