4 ms·
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
by vorpalhex 7y ago
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
- deleted 7y ago[deleted]
- nickserv 7y agoI can understand they need to make money, but still a bit shady. Honestly though it's not something critical for my needs. Now if they could lower the resource hogging a bit, that would interest me... Maybe even pay for that.
- jrockway 7y agoI use ELK for Kubernetes and network device logs, and I'm very much with you -- full text search is great, but it sure can be slow, even when running on $1000/month of AWS hardware. The conclusion that I've reached is that the whole lucene model for logs is kind of outdated. Why am I tuning Java GC params to run "grep foo /logs". I think computers today can do fine with sharded flat files, a minimal index ("which node contains logs from pod foo-2387438-2384738 at 12:34AM"), and then just scale horizontally over (log messages, searches). I hope my friends over at Tailscale are doing that and I can just move off ES entirely ;)
- ryanworl 7y agoIs Tailscale building a logging product?
- vorpalhex 7y agoELK stack user here - we actually found logstash to be our bottleneck. Changing it out for fluentd fixed our woes.
- nickserv 7y agoSame here, fluentd is much better, performance wise. But then I had to give ES more RAM because it couldn't take the hammering. In fact, increasing the throughput to ES was causing some pretty spectacular crashes, with the /var/log partition at 100% because of the verbosity of the dumps.
- majkinetor 7y agoLogstash sucks from both operational and developing perspective. I replaced it everywhere I could by sending structured logs directly from the app or by using newer integrated beats features.
- ReidZB 7y agoI believe Loki [1] is intended to basically run "grep foo" at scale (plus some extra niceties like labels). I haven't used it, but it seems interesting. [1]: https://grafana.com/loki https://grafana.com/loki
- zaphirplane 7y agoWhy don’t you want to pay for a feature that you need? The company that pays your wages makes money from selling something. Of course you sell what people need
- ipsum2 7y ago> The company that pays your wages makes money from selling something. They could be using Elasticsearch for a side project. IMO, open source projects should not be unsecured.
- Azeralthefallen 7y agoThe last time i talked to Elasticsearch about pricing, it was so extremely expensive for our use case to the point of it basically being a non valid option for us.
- igama 7y agoSame feeling...
- softwaredoug 7y agoI think what most people miss for these and similar services is you’re paying for really good, on call, white glove Elastic support. In my experience they can often go as for as to replace having a search specific ops team. The cloud hosting isn’t really where the value is.
- Azeralthefallen 7y agoI guess my issue is that we didn't want or need support. We just wanted x-pack features such as Auth and the Alerting plugins. We were already hosting it fine ourselves on AWS, as we had devops people very familiar with ES. However the price they quoted us per year was insane for our cluster size for ~20 nodes.
- zaphirplane 7y agoI looked at the price of a Tesla the other day and thought it was too expensive. doesn’t really say much, I could be in a bad financial position, Tesla could be expensive or I have a different preference to spending my money or I don’t love the environment enough ;)
- mattmcknight 7y agoIt is too late. I've stuck with Solr and things are good.