DEVOPSdigest

Undo announced the availability of LiveRecorder 5.3.

The newest version of its flagship product now offers Post Failure Logging and Log Jump functionality to all users. Codenamed Gouda, this update enables developers to achieve Mean Time To Resolution (MTTR) of software failures quicker and more efficiently in either test or production.

Post Failure Logging reduces the time and eliminates the guesswork that needs to be spent on speculative bug fixing. It provides an efficient & easy mobile way of working to provide FAE support and resolve software problems. Once determined, a single fix can be confidently deployed once - minimizing customer service disruption.

“It is not always a viable or affordable option to either send a recording offsite to a support engineer in case IP / PII sensitive data is disclosed or to have an FAE on standby support to travel to the customer site,” said Greg Law, CTO at Undo. “Post Failure Logging generates log files in a human readable file format. The transparent log files prove that no sensitive data has been exposed. The log files can then be debugged by running a series of test queries against the application in order to detect the root cause & fix of any bugs causing the software failure.“

Log Jump enables increased observability and the ability to quickly understand bugs in terms of what happened and why. It also includes an improved workflow - combining the 100% reproducibility of a LiveRecorder recording capturing the application failure with, higher level log file indicator information.

“Why use log files at all?” said Jonathan Harris, VP of product at Undo. “If a software failure was a murder mystery book, log files would be the table of contents. You wouldn’t be able to find out ‘who dunnit’ without reading the entire book. A developer may wish to reference the log file output but would want to quickly get back to the full story detail to find a suitable conclusion to the mystery bug, and that’s what Log Jump provides.”

With the release of Gouda, LiveRecorder continues to transform the traditional, time-consuming software defect resolution workflow, introducing more efficient ways to diagnose and resolve problems. Once a software failure occurs, LiveRecorder is used to take a single recording that captures the failing process down to the instruction level, that can be replayed as many times as necessary.