zeeg

19 ms·

151.
by zeeg 8y ago
For the curious, all of this is powered by Clickhouse, which has been a phenomenal addition to Sentry's stack.
152.
Sentry launches new visibility features(blog.sentry.io)
2 points by zeeg 8y ago|1 comments
153.
Using Nginx and Sentry to Trace Errors to Logs(blog.sentry.io)
1 points by zeeg 8y ago|0 comments
154.
by zeeg 8y ago
Not sure if I still agree with what I wrote here, but related article from many years back: http://cra.mr/2011/03/08/building-cursors-for-the-disqus-api There's also an implementation in Sentry, that is
155.
Sentry raises $16M to build APM for Developers(blog.sentry.io)
2 points by zeeg 8y ago|1 comments
156.
Introducing Sentry for Rust(blog.sentry.io)
4 points by zeeg 8y ago|0 comments
157.
by zeeg 9y ago
I’m genuinely curious why you would want this? For context I’m the founder, CEO, and original author of Sentry. We provide an immense amount of data for every platform and hear the exact opposite of this sentiment (“id love to use Sentry fo
158.
by zeeg 9y ago
You want a job yet? ;)
159.
by zeeg 9y ago
The storage mechanism isn't fast/flexible enough to do anything really great. It's fairly easy for us to do precise matches (with some caveats), but given everything is cached at the database level we can't easily comput
160.
by zeeg 9y ago
It's definitely on our short list of problems to solve, but unfortunately the solution takes a bit more than traditional feature development.
161.
by zeeg 9y ago
Could you reach out to support with your account details? There's a cost to the data volume, but generally queries should respond very quickly.
162.
by zeeg 9y ago
Not sure where you'd see 200 companies (we've had more than that for most of Sentry's lifetime). Not every team lines up to a company, but napkin math I'd say we have 10k - 20k companies using our cloud service. That&#x2
163.
by zeeg 9y ago
We actually do a lot more than 20B (not sure what the number is actually pulled from), but it's also important to note that even 8000 events/sec isn't free. - 40k per event (average, it gets into 2mb territory for some) - str
164.
Dodging S3 Downtime with Nginx and HAProxy(blog.sentry.io)
302 points by zeeg 10y ago|123 comments
165.
by zeeg 10y ago
Aside we're also building a bunch of open source tooling (our entire platform is open source) around mobile, so if you're looking to roll your own or bring something in-house, we'd love to hear your feedback. https:/&#x
166.
by zeeg 10y ago
How does the integration work with Sentry? Aside, would love to explore if we can make a richer integration. We added some functionality recently which is intended to allow certain kinds of embedded data in Sentry reports (as well as aggreg
167.
by zeeg 10y ago
Please, please, don't roll your own. It seems like an easy problem at a glance, but its far from it. The more fragmentation in these communities the worse off we all are. Sentry's totally open source, and we have generous free tie
168.
by zeeg 10y ago
This is definitely a conversation we've had. In our mind, we think SaaS is the right way for our business to work. It lets us continuously ship, scale more easily, and in general provide great customer service and experiences. That sai
169.
by zeeg 10y ago
I'll echo what @robinwassen said. It's almost always going to be engineering time. We are going to have lower hardware costs at scale, but we are also going to charge a premium there (to operate our business, of course). It just e
170.
by zeeg 10y ago
We measure literal end-to-end processing time on our status page here: https://status.sentry.io/ It should never be slow, so it's possible there was a misunderstanding in how something was working, a bug in an SDK, o
171.
by zeeg 10y ago
Definitely not a license expert here. Lots of legal folk I trust would stand by "Apache and only Apache" for releasing FOSS, and I think one of the core reasons is patent protection. We may re-license Sentry at some point to Apach
172.
by zeeg 10y ago
Skimmed it a while back, but didn't realize it had centralized views. I will say our biggest challenge is mostly around PRs and community issues. We use a big ol' Excel sheet for sprint planning (inspired by my Dropbox days). You
173.
by zeeg 10y ago
Unless you want to maintain a fork we could very easily make life difficult ;) I don't have a concrete answer, but if it happens you just gotta work around it. Not much different than having a dozen competitors trying to do the same th
174.
by zeeg 10y ago
I recently started playing WoW again. Don't tell anyone!
175.
by zeeg 10y ago
It's really tough. Even basic problems are extra painful because of the limited tooling on GitHub. One major problem that is still ongoing is code review. How we act on our own mandatory code review requirements as well as make sure we
176.
by zeeg 10y ago
Billing is all based on Stripe, so its not super heavy by design. We basically just synchronize the data that's in Stripe. That's changing a bit as we work towards a new model, which requires a lot more internal systems to coordin
177.
by zeeg 10y ago
That part isn't. Not so much because we care about it being closed source (a bit), but more because there's little to no value in it being open sourced.
178.
by zeeg 10y ago
Thats a common situation, but we explicitly refuse to do that. I have a strong opinion that it doesn't represent what open source should be, and thats absolutely free software. I do understand that some things are considered necessary,
179.
by zeeg 10y ago
It's much easier to start open source, rather than tack it on after the fact. Depending on your business, it could also be a huge advantage. For us, being open source means companies like Uber and Airbnb, whom have ample engineering ex
180.
by zeeg 10y ago
There's only two things we really consider as protection of our product and brand: 1. It's a big project, we are the experts (and the only real committers to the service). We also control commit access, so unless you want to maint

More ›