News for hackers. Stuff that matters.
Re:Elastic and Amazon reach agreement on trademark infringem... by clambordan on Wednesday February 16, 2022 @06:44PM (#30367466)
We had similarly terrible experiences with AWS ES, so we moved to self-hosted Elastic. It's better but still pricey and requires more manhours dedicated to tuning.

Their move away from open-source has been unfortunate. For that and some other reasons we've ended up more impressed with Logz.io and Splunk SaaS.

Re:Elastic and Amazon reach agreement on trademark infringem... by taf2 on Wednesday February 16, 2022 @08:25PM (#30368451)
What kind of tuning do you do? We spend time but typically on upgrades… very rarely have we spent much time on tuning I’m curious what kind of tuning are people doing beyond mlock and having enough memory / nodes?
Re:Elastic and Amazon reach agreement on trademark infringem... by gcbirzan on Thursday February 17, 2022 @03:21AM (#30370718)
I mean, logz.io is okay and all, but it's quite expensive, and has a loooot of outages. I don't remember a week where we didn't have issues, the most common being log ingestion lag, which take hours to fix. That, and their API is bad: you can only query over a 2 day period and their API keys allow full control over everything.