[eropple]

As a rule, my dev environments are decoupled and have no non-local dependencies, 'cause I don't always work with an internet connection. So while I've liked Sentry at prior jobs and have consistently recommended it, I have not been using it personally on my own stuff. But recently, a number of projects I'm now working on require more elaboration on errors I've used I was just saying the other day "huh, I forgot about self-hosted Sentry, I can use that for development and I can pay them in production". But I guess I should track down another alternative that isn't going to add gigs and gigs of memory to a dev stack; I like Kafka and Zookeeper and all that as much as the next nerd but if my product doesn't need it I'm certainly not running it for an exception catcher.

The marketing spiel in this is pretty shitty, too. "You can evaluate whether you want us to handle this with the cloud!" I think I'd rather evaluate whether or not I want to use you.

As I said, my automatic recommendation has always been Sentry; I now need to reevaluate this. Any locally-hostable-for-dev,-SaaS-for-prod options I should be looking at?

[viraptor]

This looks like a big enough change that someone could fork Sentry. Disconnecting the the fancy search and reenabling sqlite shouldn't be lots of work for the next few releases. I bet there are companies that will do it in private - would be interesting to see if any of them go public though.

[eropple]

It could be, and I might also just sit on the current version in a dev environment (as I assume they won't break their public API anytime soon). But the first time I hit jank I'm going to be going "man, why did I take the path of least resistance?".