IMPLEMENTING CLIENT BASED THROTTLED ERROR LOGGING

• US 20140245082A1
• Filed: 02/28/2013
• Published: 08/28/2014
• Est. Priority Date: 02/28/2013
• Status: Active Grant

• Current Assignee: Lenovo International Limited (Lenovo Group Ltd.)
• Original Assignee: International Business Machines Corporation
• Inventors: Ricard, Gary R., Halverson, Paul S.
• Granted Patent: US 9,329,972 B2
• Time in Patent Office: Days
• US Class Current: 714/49
• CPC Class Codes: G06F 11/0706 the processing taking place on a specific hardware platform or in a specific software environment
• 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/3072 where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
• CPC Class Codes: G06F 11/3082 the data filtering being achieved by aggregating or compressing the monitored data
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 21/55 Detecting local intrusion or implementing counter-measures
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/88 Monitoring involving counting

Abstract

A method, system and computer program product are provided for implementing client based throttled error logging in a computer system. A log governor, controlled by a client of a log manager, prevents the flooding of the logs, identifies how many repetitive logs have been suppressed, and is tailored such that log suppression requirements are enabled to be specified for each individual log. A space required for the log governor features or log governing information is allocated in the client.

Claims

1. A method for implementing client based throttled error logging in a computer system comprising:

providing a log governor, controlled by a client of a log manager, using said log governor for preventing flooding of logs, said log governor performing the steps of;

enabling log suppression specifications for each individual log to be suppressed, allocating a client storage space for log governing information, and identifying a number of repetitive logs having been suppressed.

2. The method as recited in claim 1 wherein the log governor encloses a call to the log manager for depositing a particular log.

3. The method as recited in claim 1 includes providing one instantiation of the log governor for each log to be suppressed.

4. The method as recited in claim 1 wherein identifying a number of repetitive logs having been suppressed includes maintaining a count of log occurrences per unit time for each said individual log to be suppressed.

5. The method as recited in claim 4 includes constructing the log governor with time limit and log threshold parameters.

6. The method as recited in claim 1 includes the log governor depositing a summary log indicating the pertinent log information and the number of suppressed logs when a log timing threshold value is reached.

7. The method as recited in claim 1 includes the log governor depositing a summary log indicating the pertinent log information and the number of suppressed logs when a log threshold value is reached.

8. The method as recited in claim 1 includes the client selecting time limit and threshold parameters for constructing the log governor.

9. The method as recited in claim 1 wherein the client controls log activity tracking and debug information with selecting parameter values for constructing the log governor.

10. A system for implementing client based throttled error logging in a computer system comprising:

a processor,

a log governor, controlled by a client of a log manager, said log governor for preventing flooding of logs,

said processor using said log governor to perform the steps of;

enabling log suppression specifications for each individual log to be suppressed, allocating a client storage space for log governing information, and identifying a number of repetitive logs having been suppressed

11. The system as recited in claim 10 wherein the log governor encloses a call to the log manager for depositing a particular log.

12. The system as recited in claim 10 includes one instantiation of the log governor being provided for each log to be suppressed.

13. The system as recited in claim 10 wherein identifying a number of repetitive logs having been suppressed includes maintaining a count of log occurrences per unit time for each said individual log to be suppressed.

14. The system as recited in claim 10 includes constructing the log governor with time limit and log threshold parameters.

15. The system as recited in claim 14 includes the client selecting said time limit and log threshold parameters.

16. The system as recited in claim 10 includes the log governor depositing a summary log indicating the pertinent log information and the number of suppressed logs when a log timing threshold value is reached.

17. The system as recited in claim 10 includes the log governor depositing a summary log indicating the pertinent log information and the number of suppressed logs when a log threshold value is reached.

18. The system as recited in claim 10 wherein the client controls log activity tracking and debug information with selecting parameter values for constructing the log governor.