31–40 of 64 posts
We're a really happy ES customer. We've on ESv6 at the moment and it's been running amazingly for us. We've halved our storage and running costs by moving from 5 to 6.
We've always been a licensed customer and they are in front of AWS with their features (we run our k8s stack on AWS though :) )
Running Elasticsearch on K8s storing 16TB of compressed logs across 6 data nodes and ~4600 shards. We're a really happy ES customer. We've on ESv6 at the moment and it's been running amazingly for us. We've halved our storage and running costs by moving from 5 to 6. We've always been a licensed customer and they are in front of AWS with their features (we run our k8s stack on AWS though :) )
Earlier quoted context omitted.
The 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.
I 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.
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.
Earlier quoted context omitted.
Why 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
>Why don’t you want to pay for a feature that you need? It's irresponsible to charge for features such as transport security, in my opinion. Want to charge for enterprise auditing, federation, reporting and granular access control? Fine, go right ahead. But withholding basic security features like transport security and basic access control that should be core leaves a bad taste in my mouth. How many unsecured Elasti…
Really unfair to point fingers at ES. And I really don’t get why People feel they should be making money off someone’s work but don’t have to pay them. What significant os or free is your company offering
Really and genuinely confusing, does the same approach work with your lawyer, mechanic plumber electricity gas company. They do something for free you demand more for free otherwise you are at risk.
Mechanic: I’ll do the oil filter for free
You: you must also replace the brake pads for free otherwise the car isn’t safe for me
Mechanic: Go ...
Earlier quoted context omitted.
Why 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
The 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.
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 ;)
Paired with an OpenResty reverse proxy I was able to set up a reasonably secure cluster back when X-Pack was prohibitively expensive and the AWS offering wasn't under their BAA.
Big thanks to that team of contributors!
Earlier quoted context omitted.
I 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.
I 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 nod…
Earlier quoted context omitted.
I 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.
I 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 nod…
Free, not open source version. Obviously a reaction to Amazon's fork- not wanting to give them any code to pull into their version. It will be interesting to see if this is enough to retain the majority of the userbase or if we'll still see a majority migrate to the 'Open Distro' fork.
1) Amazon did not actually fork elasticsearch or maintains any patches against it.
2) Elasticsearch does in fact provide completely OSS distributions and docker images for their products.
3) Amazon has created several OSS plugins for Elasticsearch that they bundle with their open distro that compete directly with what Elasticsearch does in their non OSS add-ons to their product.
So, obviously Elasticsearch is responding to Amazon by ensuring there's little functional gap with the stuff you get for free.
I'd argue most new users are still better off on elastic cloud vs amazon's hosted version of their distro and should not be attempting to run this themselves. I've used both and would pick elastic cloud every time for the simple reason of being more reliable and easy to deal with (e.g. backups, upgrades, cluster topology changes, etc.). Also, it seems they are quite competitive on price/performance.
For reference, we pay about 170 Euro a month for a simple setup that takes care of all our logging (couple of GB worth of logs / day). I'd hate running blind without that. IMHO at those prices, self hosting is not worth the effort (devops time required to do it would pay for several years of hosting).
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
Why 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
Roles, okay. Not TLS.
Security should almost always be a baseline requirement before something goes up for public sale.