Top all-time · #6323
A
Airbrake
Company blog · airbrake.io/blogprogrammingweb
Airbrake is the company blog at airbrake.io, writing about programming and web. Since 2012, 13 different Hacker News readers have linked it 15 times, most often “Airbrake is down. Go can't scale?”. No feed was found, so read it on the site itself.
15mentions?
13HN people?
2012–2020first – last linked?
Too few sampled comments (12) to say how often HN recommends it.?
Why HN links it
HN commenters mention Airbrake as an exception and error-tracking service, often in tool roundups. Linked pages include its blog, security page and a Chrome extension post; comments do not judge the writing.
Summarised by Claude from a sample of 12 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Airbrake is down. Go can't scale?4 people · 4 mentions · first linked 2012-06-29
- /2 people · 2 mentions · first linked 2012-01-31
What Hacker News says?
One thing this glances over is that you should have something monitoring your production systems to make sure that they are running correctly. To start with get something to monitor errors/exceptions and email you. To name a few services: https://airbrake.io/ https://rollbar.com/ https://github.com/errbit/errbit (can be hosted on Heroku for free) Also make sure that you have accessible logs that log useful informati…
Comment linking /
on “How to Deploy Software”Submitted The State of Client side JavaScript Error Reporting as a story · 38 points
HN discussionAwesome, great to see Instrumental ( https://instrumentalapp.com/ ) in your list. I'm one of the folks working on it, would love to hear your thoughts on us. Some quick reviews of some of the products listed: * Lighthouse ( http://lighthouseapp.com ) - Bug Tracker - good for keeping track of simple stuff last I used it (~2 years ago), but Github Issues obviated its use for me. * Pivotal ( http://www.pivotaltracker.c…
Comment linking /
on “Ask HN: Tools of the trade, 2013 edition”Submitted 4 Top Reasons for Early Bugs Fixing Strategy as a story · 2 points
HN discussionAirbrake ( http://www.airbrake.io ) Jenkins New Relic ( http://www.newrelic.com ) Jira ( http://www.atlassian.com/software/jira/overview )
Comment linking /
on “Ask HN: Tools of the trade, 2013 edition”Submitted Airbrake is down. Go can't scale? as a story · 1 points
HN discussionHere are a few that we use. Airbrake ( http://airbrake.io/ ) - Exception logging. Campfire ( http://campfirenow.com/ ) - Chat. Librato ( https://metrics.librato.com/ ) - Hosted graphing. Mixpanel ( http://mixpanel.com/ ) - Analytics, people tracking. Pagerduty ( http://www.pagerduty.com/ ) - Monitoring alerts. Sendgrid ( http://sendgrid.com/ ) - Sending emails. Sprintly ( https://sprint.ly/ ) - Project management. T…
Comment linking /
on “Ask HN: Tools of the trade, 2013 edition”Of course there's nothing wrong. My only point is quite the opposite. The post I was responding to suggested "Since he is a rocket scientist, it is unlikely that he would be able to code the frontend, and would require help", which is absurd. Given Mr. Munroes obvious interest in programming and computers, (see comics: https://xkcd.com/1180/ https://xkcd.com/1172/ https://xkcd.com/1168/ http://xkcd.com/1137/ http://…
Comment linking /blog/internet/best-programming-xkcd-comics
on “Notes on XKCD's “Pixels””Full disclosure, I run product at http://airbrake.io . We've always had high demand for Javascript error reporting. We've been slowly building out a new notifier which address the importance of page load and capturing errors without blocking the page load. https://github.com/airbrake/airbrake-js One of the main problems is clients / IE, not only on how they throw errors but also standards of source-map support and s…
Comment linking /
on “A Better Way to Track JavaScript Errors”> Also tools such as Airbrake or Sentry often send all your ENV variables to the error collection server, effectively exposing your secret values. That only happens if whoever deployed those services screwed up badly and failed to configure any kind of filtering. I mean, airbrake specifically refers to their filtering system as best practices to avoid leak sensitive data. https://airbrake.io/product/security You're…
Comment linking /product/security
on “Don't use ENV variables for secret data (2017)”Here at UserVoice, we're in love with: * http://trello.com Easy card management for tracking all of our projects and bugs. We've got boards for every department. * http://hipchat.com Fantastic way to chat in rooms or with individuals. Keeps our two offices connected. * http://argylesocial.com Fantastic social media monitoring, publishing, and most importantly, measurement. * http://airbrake.io Error collector, which…
Comment linking /
on “Ask HN: Webapps you can't live without?”@mjaneczek, this is a cool project and a nice take on yet another error tracking service. We built this feature into Airbrake back in 2012, https://airbrake.io/blog/extension/airbrake-chrome-extension but we didn't get enough feedback to get it back into local development. Projects such as https://github.com/charliesome/better_errors have been a great addition to the Rails error workflow. It's a tough business to ge…
Comment linking /blog/extension/airbrake-chrome-extension
on “Show HN: CrashBreak – Reproduce exceptions as failing tests in Ruby”A bit pricey, perhaps? That works out to a max of 1 exception every 2 minutes for the paid plan, and 1 exception every 8 hours for the free plan. By contrast the $25 plan on Airbrake[1] is 15/min and the $29 plan on Coalmine[2] is 20/min. The free plans for both are about 1-2 per minute. (Disclaimer: I work on Coalmine) But it does sound like a good service. Nice that there's some competition in this space finally--…
Comment linking /account/new?dev=true
on “Bugsnag is out of beta, launches paid plans”This might work at low traffic levels, but there are better ways. In our internal error catcher, we've seen deploys that caused 20,000+ errors in under a minute. Even when we used similar techniques to mail ourselves errors on a low traffic site, it was important to introduce dead time, not alerting again for (say) 5 mins after the first alert so as not to flood our inbox. A useful technique btw is to use a ring buf…
Comment linking /
on “The Slack Logger”I was thinking when you login to a tool like http://airbrake.io/ you see a total count. What is that number?
Comment linking /
on “Poll: How many reported exceptions are in your production environment?”