Live data from Hacker News

Sentry 8 is here

blog.getsentry.com

51–57 of 57 posts

Re: Sentry 8 is here

#51
I'm a sentry user but I'm looking at other options.

* Can't filter by additional data sent by you.

* Can't filter by Browser names instead of browser versions (i.e all Firefox instead of Firefox 35,36 etc)

* Can't ignore errors created by bots and old browsers.

Re: Sentry 8 is here

#52
@David, after upgrading from 7.7.0 to 8.0.0.dev0, sentry health api /_health/?full=1 reports {"healthy":{"CeleryAppVersionCheck":false,"CeleryAliveCheck":false},"problems":["Background workers haven't checked in recently. This can mean an issue with your configuration or a serious backlog in tasks.","Celery workers are referencing a different version of Sentry (8.0.0.dev0 vs 7.7.0)"]}

and the website has two red bars for these warning, but the reporting mechanism seems work well, and there are no warning/error records in logs.

Do these warnings have serious problem? how can I fix these warnings? (I've totally removed old sentry files in /usr/local/lib/python2.7/site-packages/sentry* and made a fresh installation)

Thanks!

Re: Sentry 8 is here

#53
@David, after upgrading from 7.7.0 to 8.0.0.dev0, sentry health api /_health/?full=1 reports {"healthy":{"CeleryAppVersionCheck":false,"CeleryAliveCheck":false},"problems":["Background workers haven't checked in recently. This can mean an issue with your configuration or a serious backlog in tasks.","Celery workers are referencing a different version of Sentry (8.0.0.dev0 vs 7.7.0)"]}

and the website has two red bars for these warning, but the reporting mechanism seems work well, and there are no warning/error records in logs.

Do these warnings have serious problem? how can I fix these warnings? (I've totally removed old sentry files in /usr/local/lib/python2.7/site-packages/sentry* and made a fresh installation)

Thanks!

Re: Sentry 8 is here

#55
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…

You could set something like this with App Enlight as everything you can interact with via API calls.

Re: Sentry 8 is here

#56
post #8

Earlier quoted context omitted.

How do you see yourself stacking up against Rollbar https://rollbar.com which has a free tier and unlimited users for paid plans? What makes your product more valuable?

We've been around for the better part of a decade and are completely open source (and free). Everything from our clients (which a lot of the community started) to every piece of the server. The only code you don't get access to is our billing infrastructure. We're also fortunate to call many of the biggest names in Silicon Valley (as well as outside) our customers. What you'll quickly find is anything that looks like…

I believe there were services like errormator, airbrake or arecibo that predate sentry, and I'm sure there were others I don't remember right now :-)

Re: Sentry 8 is here

#57
post #42

I'd really love to be able to use Sentry to collect errors in a closed .NET web app that just spams a log file. Is there a collector/raven for just tailing files (on Windows), configurable via RegEx or other parser definition? Right now we use a custom grok filter for Logstash and dump it all into Elasticsearch, but the Sentry UI sure would make life easier when something goes wrong and we have to figure out why.

There's not. The primary reason is that Sentry doesnt really match up well to traditional logging. A lot of we do involves highly structured data, and simply wouldn't be usable without that. It helps to think of Sentry more like classic crash reporting more so than modern logging. We want (and need) to know precisely what a stacktrace is, which piece is the function name, the line number, etc.

Well that's what the app is logging. Full stack traces. ;) I can think of lots of apps that do just that. If a formatted stack trace is truly what you need to ingest, maybe I should look into contributing a "Raven" for generic systems that log stack traces.
Post reply on HN