Sentry 9.1 and Upcoming Changes (opens in new tab)

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?

It must be hard to maintain their open source product. I can imagine it’s difficult to have 2 different backends that scale from self hosted to the thousands and thousands per second of the cloud. Along with the searching, HA, etc

Kind of off-topic, but with the direction GitHub is going with features and 'embrace, extend, (and to be determined with pkg repo) extinguish', I wouldn't be surprised if GH comes out with a Sentry competitor by 2021.