Rookout launches Live Logger to dynamically change log verbosity

Rookout, the creators of Live Debugger, launched Live recorder in order to make the wealth of information hidden in production logs more accessible. They intend to achieve this by providing the ability to dynamically switch an application’s log levels, log pipeline, log throughput tracking, and text and context-based filtering.

Rookout Live Logger is intended to complement the Live Debugger: it allows a developer to activate the log lines that already exist in his code, while the Live Debugger allows him to add log lines where they did not exist. not in the first place.

Its visual design follows the same approach as other “live tail” tools already available: a filter box on the top and options that can be selected on the left side. The novelty promised here is the ability to dynamically activate different log lines or levels during runtime, without having to restart the application. Presumably the Rookout SDK can achieve this through the manipulation of bytecode, which actually results in the addition and printing of new log lines. For wider adoption, it offers integration with popular logging libraries, such as Log4j, Reconnect and Winston. This basic capability should allow software engineers to collect data in real time. Currently the SDK supports JVM, .Net, Python, Node.js, and Ruby.

The functionality of Live Logger is aimed at providing the right information to the developer who is investigating a potential production issue. To achieve this, it implemented the following features:

  • Dynamic log verbosity: possibility to change the log level dynamically, without needing to redeploy and / or restart the application. You can toggle the logging level to the desired verbosity INFO, DEBUG, or even TRACE for as long as needed.
  • Text and Context-Based Filtering: Given the complexity of today’s applications, it’s difficult to comb through everything to get the right information. If possible, just enter a short string and have the information you need. Even though Live Logger prints the log lines that contain the required information, sometimes a more advanced approach is needed: only change the log lines that are printed while running users, accounts, services, or others. information relating to specific transactions. Integrated with tools that implemented OpenTracing and OpenTelemetry standards, Live Logger extracts the necessary context.
  • Log Throughput Tracking: To meet both the needs of operations that need to ensure the right amount of resources to run services, and also developers that need to have access to the information they need, Live Logger provides a resource overview I / O that is spent to send these log lines to your log storage provider.
  • Pipelining logs: After you have obtained the appropriate information available through filtering, it is time to push it to the observability pipeline. Rookout targets include the most popular log and APM management tools.

In summary, Live Logger adds new capability to the Rookout suite of tools for production debugging by providing the means to enable log lines hidden by configuration. The alignment with the visual UI design expected of a live tail tool promises rapid adoption by developers familiar with existing tools, such as DataDog, SumoLogic Where Splunk. By integrating with the most popular logging libraries and Application Performance Monitoring (APM) tools, it allows users to filter and consume data from multiple sources and share and redirect to consumers The most common.

Margie D. Carlisle