Products · Product
ELK stack
Raised as a usability problem by 10 people on Hacker News over 10 years (2015–2024), in 10 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Log searches are too slow and unreliable to be usefulUnreviewed
20152026- Before/after log queries are hard to express, and changing the query means slow waiting2024-05-26
- Logs can't be scrolled or searched as quickly as with vi and grep; must click for more lines2022-12-16
- Log searching is too slow and flaky to be useful2019-08-29
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 11 complaints
- Log search tools force a restrictive DSL built around an indexing scheme2024-07-11
- Before/after log queries are hard to express, and changing the query means slow waiting2024-05-26
- Logs can't be scrolled or searched as quickly as with vi and grep; must click for more lines2022-12-16
- ELK is a nightmare to manage at any real scale2021-05-10
- Installing ELK for log viewing took hours; documentation was obscure and overly complex2021-01-15
- Logs with mismatched field types are rejected and their data discarded2020-10-29
- Log searching is too slow and flaky to be useful2019-08-29
- Log searching is painfully slow even at small data volumes2019-08-28
- Lacks a web UI for selecting log locations, types and managing indexes, unlike Splunk2018-07-11
- Finding the right log entries is very hard in its UI2016-10-11
- Requires lots of hacking and setup before it works2015-02-01