Browse Prior Art Database

Method and System to enable dynamic logging in response to error conditions

IP.com Disclosure Number: IPCOM000234021D
Publication Date: 2014-Jan-07
Document File: 2 page(s) / 63K

Publishing Venue

The IP.com Prior Art Database

Abstract

This disclosure outlines a system that allows for logging to be enabled in the presence of error conditions. This improves the way logging is done today, where a loop consists of calling support, receiving instructions on what to enable for logging, and often restarting the program.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

Method and System to enable dynamic logging in response to error conditions
Errors occur all the time in deployed applications, and frequently users end up with little information

about why the failure occurred or what the state of the application was during the failure. Using logging statements in code is a simple way to log information helpful to the debug process, but the problem is that the logging level has to be set appropriately for these messages to appear. And often done only after the fact. If logging is set to debug on a general level, the log quickly grows out of hand and takes up far more space than is necessary, let alone the performance impact of having to write all of the log statements to disk. However, users don't always know what parts of the code are going to be error prone before a

production deployment, so it's difficult to set class or package specific logging to a higher level in anticipation of problems. Customers rarely adjust logging levels without support input anyway. All of this leaves us with a dearth of information about most failures.

This invention allows for logging levels to be adjusted automatically in the presence of failures.

The only known solution is to adjust the levels manually, and possibly restart the application, depending on how the logging is setup.

In most cases like this, the customer usually contacts support, which in turn asks the customer to set some specific logging parameters. This can take time, and in critical situ...