Implementing client based throttled error logging in a computing device

• US 9,329,972 B2
• Filed: 02/28/2013
• Issued: 05/03/2016
• Est. Priority Date: 02/28/2013
• Status: Active Grant

• Current Assignee: Lenovo International Limited (Lenovo Group Ltd.)
• Original Assignee: Lenovo Enterprise Solutions (Singapore) Pte., Ltd. (Lenovo Group Ltd.)
• Inventors: Halverson, Paul S., Ricard, Gary R.
• Primary Examiner(s): SCHELL, JOSEPH O
• Application Number:
  US13/781,305
• Publication Number:
  US 20140245082A1
• Time in Patent Office: 1,160 Days
• US Class Current: 1/1
• 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 comprising:

by first program instructions on a computing device,

communicating one or more enclosed calls for depositing an individual log into one or more logs to prevent flooding the one or more logs;

accessing one or more log suppression specifications specified by a client for each individual log;

communicating pertinent log information corresponding to each individual log to a storage space allocated by the client;

identifying a number of repetitive logs having been suppressed and

enabling client controlled log activity tracking and debug information by using the log suppression specifications specified by the client for each individual including

constructing a log class with a time limit and one or more log threshold parameters, wherein the client selects the time limit and the one or more log threshold parameters when the log class is constructed.

2. The method as recited in claim 1 includes providing one instantiation of a log class for each individual log.

3. 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.

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

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

6. An apparatus comprising:

a processor,

a log governor, controlled by a client of the log manager, the log governor for enclosing one or more calls to the log manager for depositing an individual log into one or more logs to prevent flooding of the one or more logs,

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

enabling log suppression specifications for each individual log,

allocating a client storage space for pertinent log information corresponding to each individual log, and

identifying a number of repetitive logs having been suppressed; and

enabling client controlled log activity tracking and debug information by using parameter values selected by the client and set when constructing the log governor including

constructing a log class with a time limit and one or more log threshold parameters, wherein the client selects the time limit and the one or more log threshold parameters when the log class is constructed.

7. The apparatus as recited in claim 6 includes one instantiation of the log governor being provided for each individual log.

8. The apparatus as recited in claim 6 wherein identifying a number of repetitive logs having been suppressed includes maintaining a count of log occurrences per unit time for each individual log.

9. The apparatus as recited in claim 6 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.

10. The apparatus as recited in claim 6 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.