The OptimalQ Debugging Challenge
Before adopting Rookout into their workflow, OptimalQ found that a significant amount of their developer’s time was spent researching production issues. OptimalQ found that the majority of bugs they were dealing with were very data relative and therefore difficult to reproduce and keep track of.
Their developers would turn to copious logging as a solution. They would add a large amount of logs and then use various systems to aggregate them. Then the logs would be analyzed to get the relevant data for the specific bug they were working on – hoping they caught what was needed.
The Adoption Process
“It was an amazing experience for us to onboard”, said Yechiel Levi, CTO and Co-Founder of OptimalQ. “All it took was to add a records import into our own code, and that was just a one-liner.” OptimalQ’s main concerns, in the beginning, were security-based, with their greatest concern being for their client’s privacy and how Rookout, as a sub-processor for them, would be able to maintain that high level of security.
From the start, security compliance was at the top, which was specifically a concern in regards to the data that is being transmitted. And, of course, our source code is never shared with Rookout.
