System and method for logging events of network devices

A system for logging events of network devices includes an event management module (110), an event forwarding module (120), a plurality of service modules (130), an event storing module (150), and a user interface (160). The event management module includes an event buffer (111). The service modules generate various events and classify them. Based on a callback function, the event forwarding module collects classified events and sends them to the event management module. The event management module stores events in the event storing module, and provides the events to the user interface for display according to a predefined filtering mechanism. A method for logging events of network devices is also disclosed.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a computer-enabled log recording system and method, and particularly to a system and method for logging events to manage network devices and configure the network devices by analyzing the events.

2. Related Art

With the rapid development and widespread application of electronic communications networks, more and more people are employing networks for business services and information exchange. The safe and smooth operation of a typical network relies on the provision of different services by various web servers. The services include browsing of web pages, transmission of File Transfer Protocol (FTP) files, discussion of news, and dynamic configurations of Internet Protocol (IP) addresses.

Driven by demand for the above-mentioned applications, networks are being developed in almost every corner of the globe. Effectively managing and configuring various devices connected on these networks is becoming an increasingly important and demanding task for network managers. To effectively manage and configure the various devices, the network managers often have to know the exact operation statuses of the devices. Conventionally, the operation statuses are reflected by events that occur in the devices. Therefore, obtaining and analyzing the events of each device can greatly help the managers to efficiently manage the device. For example, China Patent Publication No. CN1317745A discloses an apparatus and method for storing log data in a communication network, in which the log data are stored in a single-time writable medium such as a compact disk-recorder (CD-R), or a digital versatile disk-recorder (DVD-R). In such a system, an unauthorized user cannot change or delete the log data. Such an apparatus and method may, in some systems, efficiently prevent the original log data from being altered.

Although the above-mentioned system provides a security solution to protect log data, it does not provide managers with useful information to manage and configure the network devices. Therefore, a system and method is needed for obtaining log events from various devices on networks, and for providing the log events to managers according to practical requirements.

SUMMARY

A log event management system is provided for logging events of network devices which can assist managers to manage the network devices. One embodiment also provides a method for logging events of network devices.

In a preferred embodiment, the log event management system includes a user interface; a plurality of service modules for generating various log events; an event forwarding module for collecting the log events; an event management module for registering a callback function in the event forwarding module to collect log events, and for providing log events for the user interface; and an event storage module for storing log events. The log events may be classified into an information class, a notification class, an alert class, and a criticality class. The user interface displays the log events of different classes according to a predefined filtering mechanism.

In another embodiment, the present invention provides a log event management method for managing events in a network device. Such events may be generated by a plurality of service modules in the network device. A preferred method includes the steps of: (i) classifying the events into different classes, the classes being ranked as having different levels; (ii) registering a callback function for collecting the events generated in the network device; (iii) receiving the events; (iv) determining whether a user instruction to display the events has been received, the user instruction including a demand for defining a filtering mechanism for displaying the events; and (v) displaying one or more events according to the predefined filtering mechanism.

Other advantages and novel features of the present invention will become more apparent from the following detailed description of preferred embodiments when taken in conjunction with the accompanying drawings, in which:

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG. 1is a schematic diagram of a system for logging events of network devices in accordance with the preferred embodiment of the present invention. In this embodiment, the system includes an event management module110, an event forwarding module120, a plurality of service modules130, an event storage module150, and a user interface160. The event management module110includes an event buffer111.

In this embodiment, the service modules130may be software or firmware running on a light-emitting diode (LED) module, a driver, or another kind of functional module. Each service module130generates log events and classifies the log events into different classes. The classes of log events include an information class, a notification class, an alert class and a criticality class, which are ranked in that order from low to high in level. That is, the information class is in the lowest level, and the criticality class is in the highest level. An information class event refers to a running event of the network device. A notification class event refers to a configuration event of the network device. An alert class event refers to an event that disturbs the network device. A critical class event refers to an event that can lead to breakdown of the network device. Other classes may be used that describe information from a network device useful in network management. The event forwarding module120is provided for collecting events sent by the service modules130, and for sending the collected events to the event management module110according to special requirements of the event management module110.

In this preferred embodiment, the event management module110is a core module of the system. The event management module110maintains the event buffer111therein, and registers a callback function in the event forwarding module120. Based on the callback function, the event forwarding module120collects and sends events to the event buffer111. The event management module110further provides an indication of events to the user interface160according to a predefined filtering mechanism. In a preferred embodiment of the present invention, there are four filtering mechanisms corresponding to the four classes of events respectively. For example, when a filtering mechanism corresponding to a class of a low level applies, the event management module110provides all events with class levels equal to or higher than that low level. Other sets of classes may be used in other preferred embodiments of the present invention. A default filtering mechanism of the system is an information class filtering mechanism, which provides information class events to the user interface160. In this case, all events of the information class, the notification class, the alert class and the criticality class are provided to the user interface160. Preferably, a user can change the default filtering mechanism to a notification class filtering mechanism, an alert class filtering mechanism, or a criticality class filtering mechanism. Under the notification class filtering mechanism, the event management module110provides all events of the notification class, the alert class and the criticality class to the user interface160. Under the alert class filtering mechanism, the event management module110provides all events of the alert class and the criticality class to the user interface160. Under the criticality class filtering mechanism, the event management module110only provides events of the criticality class to the user interface160.

The event buffer111in the event management module110of this embodiment is provided for storing the events temporarily. In one preferred embodiment, the event buffer111can record a fixed number of events, such as, for example, 2,000. When the event buffer111is full, a newest event overwrites the oldest one. The event buffer111can be reset by the event management module110, by clearing all events therein. Other buffering designs may be used in other preferred embodiment of the present invention.

This embodiment also includes an event storage module150for storing events for a long time. When a network device experiences problems, the events in the event storing module150can be retrieved in order to analyze the cause of the problems.

This embodiment further includes the user interface160, which is provided for the user to communicate with the network device. The user interface160may be a command line interface (CLI) or a web interface, for example, preferably, the user interface160is a CLI. Through the user interface160, a user can alter the filtering mechanisms.

FIG. 2is a flow chart of logging events of network devices and providing the events to managers for managing the network devices, in accordance with the preferred embodiment of the present invention. At step S210, the service module130generates a plurality of events, and classifies the events into different classes. For example, a heat sink generates an overheat alert message, and classifies the overheat alert message as an alert class event. At step S220, the event management module110registers a callback function in the event forwarding module120. Thus the event forwarding module120collects the events from the service module130based on the callback function. According to the callback function, said overheat alert message is sent to the event management module110. At step S230, the event management module110receives the events. At step S240, the event management module110stores the received events in the event storage module150.

At step S250, the event management module110determines whether it has received an instruction for displaying the events. The instruction includes a demand for defining the filtering mechanism. If the event management module110has not received such instruction, the procedure is completed. If the event management module110has received such instruction, at step S260, the event management module110loads the events in the event storage module150based on the current filtering mechanism, and caches the events in the event buffer111. At step S270, the user interface160retrieves the events from the event buffer111according to a selected filtering mechanism, and displays them to the user.