The sad part is that while I really want to support Elasic here we are likely going to have to move to Amazon's Apache-licensed fork for our internal use because SSPL is incompatible with our company's open source policy.
Same here. I manage a handful of projects (10+ websites) and won't touch Elastic with a 10 foot pole now that they aren't Apache anymore. It actually doesn't matter how much they yell about their "intent." – It's an unproven license with some restrictions and I don't even want the headache and cost of having to talk to lawyers about why "it'll be fine!!" or even waste a minute during a meeting about the license impacts of solving any of the problems we face.
The ambiguity is just simply not worth the cognitive overhead. I have enough to worry about without this silly game Elastic's playing where we (customers, users) are left having to figure out the legal ambiguities and wink-winks of their new license.
And right now, we're actively searching/researching a self-hosted log analysis solution. And we've been looking at Elastic's offering and comparing it to self-hosting. Not anymore.