Mean Time To Resolution of software defects just got faster!
Today we are pleased to announce LiveRecorder 5.3, codenamed Gouda.
Gouda introduces two new feature improvements that help engineers to record, replay and resolve software failures quicker than before and more efficiently.
What's New in Gouda
- Log Jump
- Post Failure Logging
How to use LiveRecorder recordings & log files together
The new Log Jump feature is a powerful method for developers to jump from a log line of interest to the corresponding point in time in a LiveRecorder recording.
If you think of a textbook, log files are the table of contents; a LiveRecorder recording is everything else - text, images, appendices, etc. You may want to consult the table of contents to jump to a specific part of the book to understand more.
Log files rarely contain enough information to effectively determine the root cause of a problem but they are useful indicators of where problems start to occur. LiveRecorder recordings capture program execution and bugs fully, and provide developers with all the programmatic detail they need to find a fix swiftly.
With Log Jump, LiveRecorder provides a feature that maps the point in time (millisecond timestamp) where the log was output to the exact point in time in the program execution captured in the recording file (BBCount measurement).
This capability means engineers can observe the execution of a failed process to quickly understand the exact sequence of events that led to the software failure or unexpected behavior.
Once a root cause has been determined, using reverse-debugging, the issue can be resolved much quicker than when using log file analysis and other traditional methods of debugging alone - which can be cumbersome and slow.
For more technical information on how to use Log Jump take a look at our technical documentation.
A better way to get to the bottom of software failures quickly without exposing sensitive data
Post Failure Logging is LiveRecorder’s feature that generates log files in a human readable file format after a software failure occurs.
A LiveRecorder recording file is generated in the end-customers’ secure environment. This recording provides a 100% reproducible test case that captures the failure and eliminates the need for valuable time being spent on trying to reproduce the bug. The Post Failure Logging tool is then used to generate the relevant log files. The transparent log files prove that no IP/ PII sensitive data has been exposed. These logs can be queried remotely, without the recording ever leaving the secure environment of the customer site.
An engineer can work remotely to develop test log queries, away from the customer site, to determine the root cause of the problem. Once determined a single fix can be confidently deployed to production once.
For more technical information on how to use Post Failure Logging take a look at our technical documentation.
For more information about Gouda
If you'd like to see LiveRecorder 5.3 features explained and how we can help your business resolve the bugs that cause software defects faster, contact a member of our team for a demo.
And if you share our love of cheese and are curious about Gouda, find out all about it here, courtesy of Wikipedia.