Rapid production debugging solution launches by Rookout
Monday, April 30, 2018
Richard Harris |
Debugging production software is a huge challenge, and no company wants to mess with their live app or platform. Rookout hopes to solve this by giving developers the ability to grab exactly the data they need, when they need it, with just a few clicks.
Rookout has announced their launch and $4.2 million in funding by TLV Partners and Emerge. Using Rookout, a company can tackle bugs and understand issues by collecting and pipelining data on-demand, without any need for coding, re-deploying or restarting their applications.
Tackling a bug or an issue often means writing extra code, testing it, getting it approved, pushing it to production and then often discovering that it still didn't produce the data needed to solve the problem. This makes bug-hunting and data-exploration a long and complicated process that consumes R&D resources.
Rookout solves this problem by letting dev teams set up ad-hoc rules inside their production code. These rules work like non-breaking breakpoints, collecting the required data without prior instrumentation. The application keeps running as normal, while the data is collected and then sent immediately to any destination such as alerting systems, monitoring, logging and analytics applications or any generic webhook. The collected data can also be viewed on Rookout’s IDE, allowing the user to close the loop within a single view.
Already, over a dozen software companies have joined Rookout’s early adopter program and are using it on their production environments. Rookout currently supports Python, JVM and NodeJS; on AWS, Azure, Google Cloud and local servers. Rookout can be used with serverless and containerized applications, providing a vital debugging option for cloud-native code.
Rookout was founded by two Israeli low-level software engineers, Or Weis and Liran Haimovitch. They drew inspiration from their time in elite cyber-units in Israel's security services where they discovered that visibility of code is key for both attackers and defenders.
While being challenged by production debugging in other projects they ran, they realized that this practice of visibility could be applied to software development more generally.
"Fixing bugs has become coupled with the process of deploying new software,” said Rookout CEO Or Weis. “It doesn’t have to be like that. We realized that by separating debugging from the broader development process, dev teams can gain real visibility into their live code, enabling the agility and speed modern software demands."
Tackling a bug or an issue often means writing extra code, testing it, getting it approved, pushing it to production and then often discovering that it still didn't produce the data needed to solve the problem. This makes bug-hunting and data-exploration a long and complicated process that consumes R&D resources.
Rookout solves this problem by letting dev teams set up ad-hoc rules inside their production code. These rules work like non-breaking breakpoints, collecting the required data without prior instrumentation. The application keeps running as normal, while the data is collected and then sent immediately to any destination such as alerting systems, monitoring, logging and analytics applications or any generic webhook. The collected data can also be viewed on Rookout’s IDE, allowing the user to close the loop within a single view.
Already, over a dozen software companies have joined Rookout’s early adopter program and are using it on their production environments. Rookout currently supports Python, JVM and NodeJS; on AWS, Azure, Google Cloud and local servers. Rookout can be used with serverless and containerized applications, providing a vital debugging option for cloud-native code.
Rookout was founded by two Israeli low-level software engineers, Or Weis and Liran Haimovitch. They drew inspiration from their time in elite cyber-units in Israel's security services where they discovered that visibility of code is key for both attackers and defenders.
While being challenged by production debugging in other projects they ran, they realized that this practice of visibility could be applied to software development more generally.
"Fixing bugs has become coupled with the process of deploying new software,” said Rookout CEO Or Weis. “It doesn’t have to be like that. We realized that by separating debugging from the broader development process, dev teams can gain real visibility into their live code, enabling the agility and speed modern software demands."
Become a subscriber of App Developer Magazine for just $5.99 a month and take advantage of all these perks.
MEMBERS GET ACCESS TO
- - Exclusive content from leaders in the industry
- - Q&A articles from industry leaders
- - Tips and tricks from the most successful developers weekly
- - Monthly issues, including all 90+ back-issues since 2012
- - Event discounts and early-bird signups
- - Gain insight from top achievers in the app store
- - Learn what tools to use, what SDK's to use, and more
Subscribe here