We believe that with fast feedback cycles, teams can ship better quality software with more calm, confidence and speed. That’s why we’ve enhanced Airbrake with a suite of new Error, Deploy and Code Insights. Airbrake Insights is a suite of tools and metrics designed to give you a more complete… continue reading →
One of the most common questions we hear from customers is: How should I decide which problems to fix first? That’s of course a complicated, layered question and we don’t presume to have a single, one-size-fits-all answer. After all, your apps — and your team, and your customers — are… continue reading →
Two-factor authentication (2FA) adds an extra layer of security to ensure no one outside your organization can gain access to your Airbrake account and the error data you’ve sent. Airbrake already supported 2FA as part of our GitHub single sign-on feature, and now we’ve added standalone 2FA so non-GitHub users… continue reading →
As a follow up to our TLS deprecation post last August we wanted to remind all Airbrake customers that we will be deprecating support for TLS protocols v1.0 and v1.1 as well as some insecure ciphers on June 30 2018. This change is likely to only affect customers running on… continue reading →
Python 3 If you’ve already upgraded your application to Python 3 you can leverage our new Python notifier pybrake to provide more robust error reporting. pybrake is redesigned from the ground up to support Python 3.4+. pybrake‘s features include providing an async API supporting code hunks adding custom information to notices… continue reading →
Making our way through our in-depth Node.js Error Handling series, today we’ll be diving into the ERR_CONSOLE_WRITABLE_STREAM error, which is one of the many System Errors Node produces. Node throws System Errors when an exception occurs within the application’s runtime environment and such errors typically indicate that there was an… continue reading →
The 408 Request Timeout is an HTTP response status code indicating that the server did not receive a complete request from the client within the server’s allotted timeout period. The 408 Request Timeout error code appears similar to the 504 Gateway Timeout error we explored in a previous article, which… continue reading →
Making our way through our in-depth Python Exception Handling series, today we’ll be getting into the UnboundLocalError. An UnboundLocalError is raised when a local variable is referenced before it has been assigned. This error is a subclass of the Python NameError we explored in another recent article. Throughout the remainder… continue reading →
Regression testing is a form of software testing that confirms or denies a software’s functionality after the software undergoes changes. The term regression actually means “the act of reverting back to a previous state.” By extrapolating that definition into the realm of software development we can infer that regression testing… continue reading →
There are many possible errors in Node.js, so today we’ll continue our detailed Node.js Error Handling series by looking at one of the assorted System Errors Node produces, ERR_BUFFER_TOO_LARGE. Node throws a System Error when an exception occurs within the program’s runtime environment, and such errors are typically an indication… continue reading →
No more searching through log files. Capture every bug and error in your app with just a few lines of code.
Try For Free