Live data from Hacker News

Sentry 8 is here

blog.getsentry.com

21–30 of 57 posts

Re: Sentry 8 is here

#21
post #2

David from Sentry here. We're hoping to do a sort-of AMA in the future about rebuilding Sentry (and the open source approach), but if anyone has any questions about the new version I'm happy to answer them.

Sentry looks cool. I have previously tested Rollbar and Airbrake, but was deeply unsatisfied with both. The big problem I have with all these services is that you need set up each application individually: Each one is a silo, with its own notification settings, API key, and so on. We have dozens of apps (several products + lots of microservices), so this is just unacceptable. I looked into whether I could use a singl…

We're pretty similar in a lot of ways. It's definitely a pain point, but from a UX perspective its tough to solve. In theory you could manage a lot of things with the API (most of our UI runs off the API these days).

Even with the limitations, we have many people with hundreds of projects, and the general problems we see are more around notification settings than anything else. The usual suspect is that people are getting too many emails when they either want none, or they want digests.

We are giving this a lot of thought as part of our upcoming infrastructure pass. From my point of view it'd make a lot of sense if you could just have a massive stream of events and sort through them however you want. That causes a lot of challenges so it may not be feasible.

Either way its a problem we're aware of and looking to address. The simplest solution from our point of view is to allow you to configure some kind of organization-wide defaults. That won't resolve the API key constraints, but we don't feel that specifically is a pain point.

Re: Sentry 8 is here

#22
post #2

David from Sentry here. We're hoping to do a sort-of AMA in the future about rebuilding Sentry (and the open source approach), but if anyone has any questions about the new version I'm happy to answer them.

The link at the bottom of the blog post leads to a 404

Doh! Fixed ;)

Re: Sentry 8 is here

#23
post #2

David from Sentry here. We're hoping to do a sort-of AMA in the future about rebuilding Sentry (and the open source approach), but if anyone has any questions about the new version I'm happy to answer them.

Addendum to my last comment:

There really should be a requirement that SaaS services supported some kind of load/dump configuration API, where you can deal with raw config. The admin UI should be completely optional.

Most SaaS vendors don't have APIs that cover all parts of the service. Some do have decent APIs -- for example, we store our DNS records in files and use Gandi's APIs to update our zones, using a custom script (with some nice diffing capabilities), and we do some automatic configuring of Mailgun -- but APIs are always stateful and never declarative, which means that a client will always have to issue half a dozen calls to diff and converge its state. It's painful.

Re: Sentry 8 is here

#24
post #2

David from Sentry here. We're hoping to do a sort-of AMA in the future about rebuilding Sentry (and the open source approach), but if anyone has any questions about the new version I'm happy to answer them.

Addendum to my last comment: There really should be a requirement that SaaS services supported some kind of load/dump configuration API, where you can deal with raw config. The admin UI should be completely optional. Most SaaS vendors don't have APIs that cover all parts of the service. Some do have decent APIs -- for example, we store our DNS records in files and use Gandi's APIs to update our zones, using a custom…

That's an interesting idea. We're Datadog users and one behavior I like is that, while they have a fancy way to build the charts, you can simply click an advanced mode and grab the full JSON configuration (thus being able to copy paste it).

We'll give some thought into this, as it's not too far from being a possibility.

Re: Sentry 8 is here

#25

Earlier quoted context omitted.

Did you try: https://documentcloud.github.io/visualsearch/ ?

Nope. I don't think we were even aware of this project. It's pretty slick; I'd probably experiment putting it into Sentry.

Hey, I wrote that widget! I'm also a long-time Sentry user and would love to see VisualSearch.js integrated.

Re: Sentry 8 is here

#26
post #21

Earlier quoted context omitted.

Sentry looks cool. I have previously tested Rollbar and Airbrake, but was deeply unsatisfied with both. The big problem I have with all these services is that you need set up each application individually: Each one is a silo, with its own notification settings, API key, and so on. We have dozens of apps (several products + lots of microservices), so this is just unacceptable. I looked into whether I could use a singl…

We're pretty similar in a lot of ways. It's definitely a pain point, but from a UX perspective its tough to solve. In theory you could manage a lot of things with the API (most of our UI runs off the API these days). Even with the limitations, we have many people with hundreds of projects, and the general problems we see are more around notification settings than anything else. The usual suspect is that people are ge…

I see. What I don't understand is why settings need to be so granular.

For example, our company uses Slack. All notifications go to Slack. There's no need for per-project settings because it's all just one room. At some point we will probably want some projects to go to other rooms, but that's a coarse-grained exception, not something that warrants a per-project setting.

Also, if you need per-person notification settings, then surely that's part of the user's account/profile, not the project. That would be just a single dashboard page with (say) on/off sliders for each project.

In my mind, the data model used by exception trackers (including, it seems, Sentry) is wrong. There needs to be just one stream of events, tagged by things like application name that you can filter on. How those events map to things like notifications and aggregations and rules and source files and teams and so on is completely orthogonal to the stream. Those things then apply to a subset that you can modify dynamically without having to reconfigure the sender.

Re: Sentry 8 is here

#28
post #2

David from Sentry here. We're hoping to do a sort-of AMA in the future about rebuilding Sentry (and the open source approach), but if anyone has any questions about the new version I'm happy to answer them.

Can I come work for you?

Re: Sentry 8 is here

#29
post #27

I am running a Sentry 7 instance. How does the upgrade path to 8 look like? Will I lose any data?

We always recommend reviewing the CHANGES, but if you're already on 7.x it should be mostly painless.

You can't install via standard channels yet (effectively you need to install from GitHub), but otherwise there's no major concerns.

Re: Sentry 8 is here

#30
post #2

David from Sentry here. We're hoping to do a sort-of AMA in the future about rebuilding Sentry (and the open source approach), but if anyone has any questions about the new version I'm happy to answer them.

I already implemented releases a few weeks ago. They're great, thanks for that!

I'm wondering what the reasoning is behind suggesting I upload source artifacts to you as part of a release. The blog post even specifically calls out Go, which is what the majority of our application is written in. So from my understanding, uploading artifacts would allow the Sentry UI to show me exactly where we did a Sentry Dump?

On the same topic, our current deploy flow makes it a bit hard to upload specific code changes per release. It would be great if Sentry could get the code from Github directly (assuming that I login and give you access to the repo)

Thanks for Sentry, we use it daily and would have a much harder time tracing errors and monitoring overall application health without it.

Post reply on HN