System and method for electronic event logging

• US 7,415,505 B2
• Filed: 04/21/2004
• Issued: 08/19/2008
• Est. Priority Date: 06/20/2003
• Status: Expired due to Fees

• Current Assignee: Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd. (Hon Hai Precision Industry Co., Ltd.), Hon Hai Precision Industry Co., Ltd.
• Original Assignee: Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd. (Hon Hai Precision Industry Co., Ltd.), Hon Hai Precision Industry Co., Ltd.
• Inventors: He, Tang, Wang, Gonggian
• Primary Examiner(s): WON, MICHAEL YOUNG
• Application Number:
  US10/829,887
• Publication Number:
  US 20050010929A1
• Time in Patent Office: 1,581 Days
• Field of Search: 709/206, 709/207, 709/224, 714/4, 714/15, 714/25, 714/48
• US Class Current: 709/207
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: H04L 41/0609 based on severity or priority
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 63/1425 Traffic logging, e.g. anomaly detection

Abstract

An event logging system (5) includes one or more message sources for generating messages, an event logging library (54) for formatting the messages, a local event logging daemon (57) for distributing the messages, and one or more message destinations for receiving the messages. The local event logging daemon distributes the messages from said message sources to said message destinations. The message sources include one or more of an application (50), a hook (51), a kernel module (56), an internal buffer (59) and a remote event logging daemon (58). The message destinations include one or more of said hook, said internal buffer, said remote event logging daemon, a file system (52) and a mail system (53). The event logging system further includes a kernel logging daemon (55) for transmitting the messages from said kernel module to the event logging library. A related method for logging the messages is also provided.

Claims

1. An event logging system for logging messages, the event logging system comprising:

at least one message source for generating the messages;

an event logging library for formatting the messages;

a local event logging daemon for distributing the messages according to a configuration file that indicates which of said at least one message source generates the message, priority levels of the message, and how to deal with the messages; and

at least one message destination for receiving the messages;

wherein the local event logging daemon distributes the messages from said at least one message source to said at least one message destination, wherein the local event logging daemon is configured for dynamically setting up an Internet socket to transmit the messages between a remote event logging daemon and the local event logging daemon.

2. The event logging system as claimed in claim 1, wherein said at least one message source comprises any one or more of an application, a hook, a kernel module, an internal buffer, and a remote event logging daemon.

3. The event logging system as claimed in claim 2, wherein said at least one message destination comprises any one or more of a hook, an internal buffer, a remote event logging daemon, a file system, and a mail system.

4. The event logging system as claimed in claim 2, further comprising a kernel logging daemon for transmitting the messages from said kernel module to the event logging library.

5. The event logging system as claimed in claim 1, wherein the local event logging daemon is provided for dynamically setting up a UNIX domain socket to transmit the formatted messages between the event logging library and the local event logging daemon.

6. The event logging system as claimed in claim 4, wherein the event logging library is provided for transmitting the messages from said application, said hook or the kernel logging daemon to the local event logging daemon.

7. The event logging system as claimed in claim 3, wherein said internal buffer stores the formatted messages transmitted by the local event logging daemon.

8. The event logging system as claimed in claim 7, wherein the local event logging daemon reads the formatted messages stored in said internal buffer.

9. The event logging system as claimed in claim 3, wherein the local event logging daemon distributes the formatted messages to said tile system or said mail system directly.

10. The event logging system as claimed in claim 1, wherein the configuration file is configured so that it can be modified by a user such that the priority levels of the messages are changed in order to ensure logging of all important events.

17. The method as claimed in claim 10, further comprising the following step:

changing the priority levels of the messages by modifying the configuration file in order to ensure logging of all important events.

11. A method for logging messages, the method comprising the following steps:

(a) at least one message source selecting a message destination, a priority level for each of the messages and transmitting the messages;

(b) a local event logging daemon receiving the messages;

(c) the local event logging daemon distributing the messages to at least one message destination according to a configuration file that indicates which of said at least one message source generates the message, priority levels of the message, and how to deal with the message; and

wherein when said message source is a remote event logging daemon, step (a) further comprises the following steps;

(a20) the local event logaina daemon setting up an Internet socket;

(a22) the local event logging daemon monitoring the messages via the Internet socket; and

(a24) said remote event logging daemon transmitting the messages to the local event logging daemon via the Internet socket.

12. The method as claimed in claim 11, wherein said at least one message source comprises any one or more of an application, a hook, a kernel module, an internal buffer, and a remote event logging daemon.

13. The method as claimed in claim 12, wherein said at least one message destination comprises any one or more of a hook, an internal buffer, a remote event logging daemon, a file system, and a mail system.

14. The method as claimed in claim 13, wherein when said at least one message source of step (a) is said application, said hook or said kernel module, step (a) further comprises the following steps;

(a10) the local event logging daemon setting up a UNIX domain socket;

(a12) the local event logging daemon monitoring the messages via the UNIX domain socket;

(a14) said at least one message source transmitting the messages to an event logging library; and

(a16) the event logging library formatting the messages.

15. The method as claimed in claim 14, wherein when said at least one message source is said kernel module, step (a14) further comprises the step of a kernel logging daemon transmitting the messages from said kernel module to the event logging library.

16. The method as claimed in claim 15, wherein step (b) further comprises the step of the event logging library transmitting the formatted messages to the local event logging daemon via the UNIX domain socket.