Another week, another massive shipment. After months and months of mad science development, private beta testing (thanks!) and more tweaks and polish, Opbeat for Node.js is now available to everyone!
Since the launch of our in-depth performance metrics, we’ve been receiving an increasing number of requests to support additional languages, and finally it’s time to take the big step. After many months of hard work, we’re thrilled to open Opbeat to our first additional language, and announce our Opbeat for Node.js private beta!
Every developer has shipped memorable errors in their code, it’s part of the job description and the learning curve. But are there any trends for when these errors occur? Is there a link between the number of releases made and the number of errors generated? And how does it fit with the working hours of the development team?
As far as long-anticipated announcements go, this is most certainly one of them. The success of our iOS app has prompted many requests for an Android version. The good news? Opbeat for Android is now available.
Opbeat’s mission is to help developers operate their code together. And to do so, we have found that you need at a minimum four key components: Application performance metrics, release tracking, error logging and workflow.