21–30 of 64 posts
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.
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
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 Elasticsearch servers have been popped, leading to data breaches as a direct result of this decision?
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.
Also note that you'll want to go to the features page and hit the disclosure triangle on the 'Security' feature. This is very much a subset of their security features- no IP filtering, AD/LDAP integration, SAML or many other security oriented features. https://www.elastic.co/subscriptions
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.
I was under the impression that they already opened the code for X-Pack features.
Earlier quoted context omitted.
I was under the impression that they already opened the code for X-Pack features.
Were these features licensed in such a way that you could freely use them, though? Or was it 'open' as in "you can see the code" but it's not FOSS?
Too little too late? Trying to charge for TLS was a very poor move and it's made me not trust ElasticSearch...
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.
Interesting. Three hours ago someone in our Ops team shared a link to "Open Distro for Elasticsearch" [1] and it's also featured on the AWS console login page. Is this a very rushed reaction to it? Or is this related? I would really love to have a clarification of what's happening in that space. [1] https://opendistro.github.io/for-elasticsearch/
https://github.com/opendistro-for-elasticsearch/security
which has feature parity with the free version elastic just released afaict.
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.
I was under the impression that they already opened the code for X-Pack features.
https://news.ycombinator.com/item?id=16487440
Summary -- vague use of the word 'open' and exclusive use of free in the beer sense, led to some significant angst about what this means for end users.
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…