Why dynamic logging is critical to business continuity.

CEO Release. Over the past two decades, he has led data-driven businesses, products and R&D teams from startups to government organizations.

Companies in every industry are struggling to downsize and cut unnecessary costs. However, investments in technology and modernization are constant and even continue to grow. From our perspective, this is a wise decision that highlights the fact that investing in IT and using better equipment leads to lower costs and higher ROI.

Now, that’s not to say that large enterprise contracts aren’t seriously reviewed when it comes time to renew them. As a technology vendor, if you don’t have an active relationship with your customers, don’t be surprised if churn is higher than usual as companies try to make prudent investments. But the thing about smart technology—which more and more CFOs are starting to understand (hence the rise of FinOps)—is that the new capabilities and greater productivity unlocked by good technology far outweigh the cost concerns. Any software vendor worth their salt can easily demonstrate that value.

And I can’t think of a simpler way for companies to eliminate unnecessary costs and increase productivity than to adopt dynamic logging.

The traditional world of the log

In an ideal world, developers wouldn’t need to waste precious time writing log lines, costing them storage, finances, and even application performance. Instead, developers can effortlessly extract the data they need on demand. But for most companies, logging hasn’t changed in decades.

So what do most of us do? As developers, we dread the situation where we need to debug an issue and don’t have the necessary logs, so we insert a log line every few lines of code. This is a universal concern, so unfortunately the trend has become to document everything. The reality is that trunks quickly become expensive to store and noisy in size.

The solution: dynamic logging

The idea behind dynamic logging is that you can change your logging verbatim without stopping the application or writing new code. In other words, when there is no problem, the logs can be kept in a low verbatim state, and once a problem that needs troubleshooting occurs, a developer can click and add verbatim to collect all the necessary information. Button.

There are a few solutions for variable logs on the market. Our company has a live logger product, IBM has its own dynamic logging solution, and Pixie Labs is currently working on a product (alpha) that solves the problem of converting static logs to dynamic logs in Go. And we see more flexible solutions than the traditional log players themselves.

Unfortunately, we are not at the point where we can completely eliminate stems. But dynamic logging is a step in the right direction to reduce noise, reduce costs and increase productivity.

So how does it work?

Each entry entry is divided into the following weighting categories and correction categories listed from lowest impact to highest:

Log categories

• Trace
• Correction
• Information
• Be warned
• Error
• Killer

You can dynamically change the section of the log without having to quit the application, which affects how many words the log creates. Typically, this is if the log is highly verbose and not relevant to the issue, but with dynamic logs you can leave logs in perpetual trace or debug mode until you choose to change the section dynamically. In flight to an error or fatality.

This dynamic tool can be manipulated by bytecode, commonly seen in cybersecurity but uncommon among developer tools. Combined with modern debugging, these tools give developers quick access to the code-level data they need to troubleshoot and understand complex modern applications.

What to look for in a flexible logging solution

1. The ability to change the words of the logs Without You have to write new code or restart the application. If this is not possible, the solution is not flexible and does not offer real-time capabilities.

2) Ability to search and filter missing log data dynamically. This allows your engineering team to enhance application components and change the terminology for specific files, functions, and services.

3. Deep integrations with your existing recording tools. In the future, every recording device will have dynamic capabilities, but this is not the state of the world today. Tearing out and replacing traditional tree solutions you may already have in place is a big undertaking. Offering seamless integrations, next-generation logging solutions integrate your existing logging data to make it more flexible and actionable.

For most organizations, moving to dynamic logging is a no-brainer. It improves costs, reduces noise and makes your engineers’ lives more enjoyable. You can retrieve the data you need when you need it—no need to be bogged down by logs and looking for a needle in a needle when troubleshooting.

The Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Am I eligible?