Adaptive application logger

• US 9,626,240 B2
• Filed: 09/25/2014
• Issued: 04/18/2017
• Est. Priority Date: 09/25/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Rajkovic, Eric Bertrand, Chikovani, Eugene, Steinmeier, Oliver
• Primary Examiner(s): GUYTON, PHILIP A
• Application Number:
  US14/496,427
• Publication Number:
  US 20160092295A1
• Time in Patent Office: 936 Days
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0781 Error filtering or prioritizing based on a policy defined by the user or on a policy defined by a hardware/software module, e.g. according to a severity level
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence

Abstract

Embodiments of the invention provide systems and methods for logging of messages in a development environment. More specifically, embodiments of the present invention provide dynamically adaptive logging of runtime messages generated by an application. These embodiments provide a way to handle the volume of information stored in the logs by dynamically changing the severity associated with generated messages based on previous code path execution. Embodiments can use a set of metrics to replace the usual static log level associated with the code by the developer. For example, such metrics can include but are not limited to a cost-based (storage volume on disk), an exception-based (weight increase in catch block), and/or a crowd-based (community can vote down noise). As a result, embodiments can provide more detailed information when the error is recurring for a particular user but without generating so much information as to make the log difficult to use.

Claims

1. A method for adaptively logging runtime messages related to an application, the method comprising:

detecting a predefined condition of the application;

determining an execution state of the application at a time the predefined condition is detected; and

dynamically determining whether to generate a log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition includes;

determining whether the predefined condition of the application has been previously detected; and

in response to determining the predefined condition has not been previously detected, suppressing generation of the log message associated with the detected predefined condition, saving the detected predefined condition and the determined execution state of the application at the time the predefined condition is detected, and weighting the detected predefined condition.

2. The method of claim 1, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition further comprises, in response to determining the predefined condition has been previously detected:

determining based on a set of one or more metrics whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition;

in response to determining to suppress generation of the log message associated with the detected predefined condition based on the set of one or more metrics, suppressing generation of the log message associated with the detected predefined condition and increasing the weighting of the detected predefined condition; and

in response to determining to generate the log message associated with the detected predefined condition based on the set of one or more metrics, increasing the weighting of the detected predefined condition and generating the log message associated with the detected predefined condition.

3. The method of claim 2, wherein the metrics comprise one or more cost-based metrics.

4. The method of claim 2, wherein the metrics comprise one or more exception-based metrics.

5. The method of claim 2, wherein the metrics comprise one or more crowd-based metrics.

6. The method of claim 2, further comprising determining whether to continue adaptively logging runtime messages associated with the detected predefined condition of the application.

7. The method of claim 6, further comprising, in response to determining to not continue adaptively logging runtime messages associated with the detected predefined condition for the application, halting logging of messages associated with the detected predefined condition for the determined execution state of the application.

8. A system comprising:

a processor; and

a memory coupled with and readable by the processor and storing therein a set of instructions which, when executed by the processor, causes the processor to adaptively log runtime messages related to an application by;

detecting a predefined condition of the application;

determining an execution state of the application at a time the predefined condition is detected; and

dynamically determining whether to generate a log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition includes;

determining whether the predefined condition of the application has been previously detected; and

in response to determining the predefined condition has not been previously detected, suppressing generation of the log message associated with the detected predefined condition, saving the detected predefined condition and the determined execution state of the application at the time the predefined condition is detected, and weighting the detected predefined condition.

9. The system of claim 8, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition further comprises, in response to determining the predefined condition has been previously detected:

determining based on a set of one or more metrics whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition;

in response to determining to suppress generation of the log message associated with the detected predefined condition based on the set of one or more metrics, suppressing generation of the log message associated with the detected predefined condition and increasing the weighting of the detected predefined condition; and

in response to determining to generate the log message associated with the detected predefined condition based on the set of one or more metrics, increasing the weighting of the detected predefined condition and generating the log message associated with the detected predefined condition.

10. The system of claim 9, wherein the metrics comprise one or more cost-based metrics.

11. The system of claim 9, wherein the metrics comprise one or more exception-based metrics.

12. The system of claim 9, wherein the metrics comprise one or more crowd-based metrics.

13. The system of claim 9, further comprising determining whether to continue adaptively logging runtime messages associated with the detected predefined condition of the application.

14. The system of claim 13, further comprising, in response to determining to not continue adaptively logging runtime messages associated with the detected predefined condition for the application, halting logging of messages associated with the detected predefined condition for the determined execution state of the application.

15. A computer-readable memory comprising a set of instructions stored therein which, when executed by a processor, causes the processor to adaptively log runtime messages related to an application by:

detecting a predefined condition of the application;

determining an execution state of the application at a time the predefined condition is detected; and

dynamically determining whether to generate a log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition includes;

determining whether the predefined condition of the application has been previously detected; and

in response to determining the predefined condition has not been previously detected, suppressing generation of the log message associated with the detected predefined condition, saving the detected predefined condition and the determined execution state of the application at the time the predefined condition is detected, and weighting the detected predefined condition.

16. The computer-readable memory of claim 15, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition further comprises, in response to determining the predefined condition has been previously detected:

determining based on a set of one or more metrics whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition;

in response to determining to suppress generation of the log message associated with the detected predefined condition based on the set of one or more metrics, suppressing generation of the log message associated with the detected predefined condition and increasing the weighting of the detected predefined condition; and

in response to determining to generate the log message associated with the detected predefined condition based on the set of one or more metrics, increasing the weighting of the detected predefined condition and generating the log message associated with the detected predefined condition.

17. The computer-readable memory of claim 16, further comprising determining whether to continue adaptively logging runtime messages associated with the detected predefined condition of the application and in response to determining to not continue adaptively logging runtime messages associated with the detected predefined condition for the application, halting logging of messages associated with the detected predefined condition for the determined execution state of the application.

18. A method for adaptively logging runtime messages related to an application, the method comprising:

detecting a predefined condition of the application;

determining an execution state of the application at a time the predefined condition is detected; and

dynamically determining whether to generate a log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition, wherein dynamically determining whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition includes;

determining whether the predefined condition of the application has been previously detected; and

in response to determining the predefined condition has been previously detected;

determining based on a set of one or more metrics whether to generate the log message associated with the detected predefined condition or to suppress generation of the log message associated with the detected predefined condition;

in response to determining to suppress generation of the log message associated with the detected predefined condition based on the set of one or more metrics, suppressing generation of the log message associated with the detected predefined condition and increasing a weight of the detected predefined condition; and

in response to determining to generate the log message associated with the detected predefined condition based on the set of one or more metrics, increasing the weight of the detected predefined condition and generating the log message associated with the detected predefined condition.

19. The method of claim 18, wherein the metrics comprise one or more cost-based metrics, exception-based metrics, or crowd-based metrics.

20. The method of claim 18, further comprising:

in response to determining the predefined condition has not been previously detected, suppressing generation of the log message associated with the detected predefined condition, saving the detected predefined condition and the determined execution state of the application at the time the predefined condition is detected, and determining the weight of the detected predefined condition.