JP2002366395A - Log output information management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To control the output of log information without changing a program constituted of a plurality of module groups. SOLUTION: A log output information management system is provided with a log management means which manages only one log mechanism existing in the program, one or more output means by which the program writes log message, and an output control means which decides whether log messages outputted to the output means it to be outputted or not, and the output control means is connected to the output means or a higher-order output control means to connect all output control means to a tree structure having the log management means as the top.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a method for modifying a program constituted by a plurality of module groups without changing the program.
The present invention relates to a log output information management system capable of controlling output of log information.

[0002]

2. Description of the Related Art Generally, a program mounted on a computer accumulates message information called a log or outputs it to another program in the course of execution. The log information is used for various purposes such as auditing access history, restoring a state when a failure occurs, notifying when a failure occurs, and analyzing a bug in the program itself.

Conventionally, as a technique for controlling log message data generated in a process of executing a business program mounted on a computer, there is a technique disclosed in Japanese Patent Publication No. 11-296415. In Japanese Patent Publication No. 11-296415, a log rank setting table in which rank data is set and an output level setting table for variably storing log levels to be output are provided for various types of log message data. When log message data is generated in the course of execution, by referring to the log rank setting table and acquiring the rank of the log message data, whether the acquired rank is equal to or higher than the log level stored in the output level setting table is determined. A technique is disclosed in which the log message data is output to a log output file only when the rank is equal to or higher than the log level.

[0004]

However, the above-mentioned prior art has the following problems to be solved.
That is, in recent years, software has often been constructed using an object-oriented programming language such as C ++ or Java. A significant feature of this type of programming language is that code reusability is extremely high as compared to procedural languages such as C. This code can be reused at the object level (binary level) as well as at the source level,
It is common to create a piece of software by combining various reusable objects (modules) as components.

When such a program creation method is used, the creation of each module can proceed independently of the creation of other modules, so that high development efficiency can be improved. However, there arises a problem that information operation at a system level becomes difficult such as output of log information. This is because the absence of information sharing means between modules enables independent development of modules.

From the viewpoint of log output, when the above-described conventional technique is applied to a program composed of a plurality of module groups, a log rank setting table, an output level setting table, Needs to be prepared, which causes a problem that the setting becomes extremely complicated. Furthermore, since a means for managing them collectively is not provided, there is a problem that it is impossible to make settings for outputting desired log information unless the internal structure of the software is established.

[0007]

SUMMARY OF THE INVENTION A log output information management system according to the present invention solves the above problems by providing a log output for managing log message information generated in the course of executing a program constituted by a plurality of modules. An information management system, comprising: a log management unit that manages a single log mechanism existing in a program; one or more output units for writing a log message by the program; and a log message output to the output unit. Output control means for determining whether output is possible or not, and by connecting the output control means to the output means or a higher-level output control means, all the output control means have a tree structure having the log management means at the top. Is connected to.

Further, in the log output information management system of the present invention, in the judgment of the output control means, if an explicit output setting is made in the output control means, the explicit output setting is made according to the setting. If not, the determination is delegated to a higher-level output control means.

Further, in the log output information management system according to the present invention, when an explicit output setting is not performed in the higher-level output control means, a higher-level output control means which is a root node of the tree structure. The determination is delegated to

[0010]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below using specific examples. <Specific Example 1> FIG. 1 is a program configuration diagram for explaining a first embodiment of a log output information management system according to the present invention. This configuration diagram shows objects related to log output arranged in the program. In the specific example 1, it is assumed that the program includes the first module 102 and the second module 105.

In FIG. 1, a log manager 101 comprises:
It manages the entire log output mechanism in a program, and is an object that is guaranteed to exist only once in a process. This log manager 101
Log channel 103 and log channel 106 to be described later
Connection (communication) with the log channel 103 and the log channel 106 to obtain setting information such as a settable output level from the log channel 103 and the log channel 106 and to set the log output level and the like for the program to each log channel 103 and the log channel 106 Has the role of communicating.

Module 102 and module 105
Are first and second modules respectively constituting a program. Each of the modules 102 and 105 has a log channel 103 and a log channel 106 for managing log information in each module.
Are present one or more times.

Log channel 103 and log channel 1
06 is a log channel that controls one or more output streams. Each log channel 103 and log channel 106 belong to the log manager 101 and have one output stream 104 associated as a level or a plurality of output stream groups 10 associated as levels.
7 (communication). The log channel 103 connects (communicates) with only one output stream 104, and the log channel 106 connects (communicates) with a plurality of output stream groups 107.

Log channel 103 and log channel 1
06 has the log output level and the setting information regarding the output destination of the log message, and upon receiving the log message from the output stream 104 or 107 under the management, determines whether or not to perform the log output. Perform based on. If the log channel has not been explicitly set for output, the log manager 101
Performs processing according to the default value for the output set in.

The output stream 104 and the output stream group 107 are stream objects for log output. The program writes log messages to the output stream in each module. For example, when a program described in the first module 102 performs log output, a message is written to the output stream 104. Also, a plurality of output stream groups 107 are associated with the log channel 106. These output streams are assigned and generated for each of a plurality of set output levels.

The management client 108 is used by the operation manager of the program. The operation manager makes settings for the running program via the management client 108 for the log manager 101. All log channels (such as log channel 103 and log channel 106) existing in the program (such as module 102 and module 105) are stored in log manager 101.
Since it is connected to (communicated with) the operation manager can perform setting work without knowing in advance the internal structure of the program and information unique to each module. For example, if a module in any program fails,
It is possible to shift only the module to the output mode for debugging without stopping the program.

<Operation of Specific Example 1> Next, the log output process (operation) of the first embodiment of the present invention configured as described above will be described.

[Step 1] First, the second module 1
05 generates the log channel 106. If this generation is the first log channel in the program, the log manager 101 is automatically generated internally at the same time. If the log channel is the second or subsequent log channel, it connects (communicates) with the already generated log manager 101.

[Step 2] The program constituting the second module 105 requests the log channel 106 to output a plurality of levels of logs. The log output level is, for example, the following level. Failure level A level that outputs a log only when a serious failure that affects the operation of the program occurs. Warning level In addition to the information on the failure level, this is the level at which there is no problem in the operation of the program but a log is output when any failure is detected. Notification level In addition to the information up to the warning level, this is the level that outputs information for grasping the outline of the internal state of the program, such as changes in the state of the program. Tracking level In addition to the information up to the notification level, this is the level at which information about the program operation, such as information on method goals in the program, is grasped. Debug level In addition to information up to the trace level, a level that outputs very detailed information for debugging programs.

[Step 3] The log channel 106 generates output streams 107 for the requested number of levels and issues them to the program.

[Step 4] The program outputs a log message to a predetermined output stream in the output stream group 107.

[Step 5] The output stream that has received the log message transmits the message to the log channel 106 as it is.

[Step 6] Upon receiving the log message, the log channel 106 compares the output level associated with the stream from which the log message is output with the set level at which output is permitted. If the stream level exceeds the set level and satisfies the conditions that can be output,
The log channel 106 writes a log message to an output destination such as a file. On the other hand, when the conditions that can be output are not satisfied, the log channel 106 ignores the log message. If the output level is not explicitly set in the log channel 106, the determination is made according to the default value set in the log manager 101.

The operation in the second module 105 has been described above, but the same processing is also performed in the first module 102.

<Effect of Specific Example 1> According to the specific example 1, as described above, it is guaranteed that only one log output stream existing in the program exists in the program. Since the management is performed by the log manager 101, the operation manager of the program can perform setting work for all output streams by accessing the log manager 101.

Further, the operation manager operates the log manager 10.
Since it is possible to acquire information that can be set from the first step, there is no need to know in advance the internal structure of the program and information about each module, and the output level and output destination can be easily set even for a huge and complicated program. It becomes possible.

Further, by using the setting information of the log manager 101 in common as the default value of the output information, the default value of the log manager can be set without performing the output setting for each log channel. By doing so, it is possible to change the output state collectively.

Furthermore, since the log manager 101 is created implicitly, each module creator can perform development without worrying about cooperation with other modules.

<Specific Example 2> FIG. 2 is a program configuration diagram for explaining a second embodiment of the log output information management system of the present invention. This configuration diagram shows objects related to log output arranged in the program as in the first embodiment.

The log manager 201 manages the entire log output mechanism in the program, and is an object that is guaranteed to exist only once in a process. The log manager 201 has a role of acquiring setting information such as an output level that can be set from a log controller 203 described later, and transmitting settings such as a log output level for a program to each log controller.

The module 202 is a first module constituting a program, and the module 206 is a first module.
This is a second module created by inheriting the module 202 of FIG.

The log controller 203 controls the log output in the module. The module using the log mechanism in the specific example 2 needs to own one or more log controllers 203 in the object. The log controller 203 has a role of controlling log output in the module, and manages information on a predetermined output level, an output destination, and the like. In this specific example, it is assumed that the log controller 203 is an object that is managed by one log manager 201 and that can be accessed from a module of the inherited class (for example, the module 206).

A log manager 201 is created at the same time that the first log controller is created in the program. This guarantees that only one log manager 201 exists in the program.

The log channels 204, 207, 208 and 210 are log channels for controlling an output stream or a lower log channel. Each log channel is under the control of the log controller 203 or a higher-level log channel, and manages one output stream (or stream group) or one or more log channels. In this specific example, the log channel 204 manages only one output stream group 205 and the log channel 207.
Manages two log channels 208 and 210.

The log channel owns the setting information on the log output level and the log output destination, and upon receiving a log message from an output stream under control or a log channel, determines whether or not to perform log output. This is performed based on the setting information. If the output level information is not explicitly set in the log channel, the log message is forwarded to the upper log channel. Further, when the log channel is directly connected to the log controller 203 like the one indicated by the log channel 204 (the log channel 204), the determination is made according to the default value regarding the output set in the log controller 203.

The output stream group 205 and the output streams 209 and 211 are stream objects for log output. The program writes a log message to the output stream in the module to which it belongs. For example, when a program described in the first module 202 performs log output, a message is written to a predetermined output stream of the output stream group 205.

In this specific example, the management client (the management client 108 in the specific example 1) is omitted, but also in this specific example, the log output level in the running program is dynamically set. It goes without saying that it is used similarly.

<Operation of Specific Example 2> Next, the log output process (operation) of the second embodiment according to the present invention configured as described above will be described.

First, the formation (operation) of the log output mechanism will be described. [Step 1] The creator of the first module 202 creates a log controller 203, a log channel 204 under its management, and an output stream group 205 under its management in a program. At this time, the log controller 203 executes the inherited class (the module 206
Etc.) so that they can be referenced directly or indirectly. Further, the program in the first module writes a log message to any of the output stream groups 205.

[Step 2] Next, the first module 20
The creator of the second module 206 that inherited the second
Log controller 203 published by the module 202
A log channel 207 is created so as to connect (communicate) with the log channel.

[Step 3] Second module 2
The creator of 06 creates a log channel or an output stream below the log channel 207 as necessary. In this example, two output streams 209 and 211 are created. In the second module, log information is written to these output streams 209 or 211.

By generating a log channel in this way, even if a class is inherited and created, a certain module can be configured to form a tree structure with one log controller 203 as a vertex.

Next, the log output process (operation) of the log output mechanism thus formed will be described. Here, the output control for the output stream 209 will be described as an example.

[Step 1] First, the second module 2
The program in 06 writes a log message to the output stream 209.

[Step 2] The output stream 209 sends the input message as it is to the log channel 208 which manages this stream.

[Step 3] The log channel 208 determines whether an explicit output setting has been made for this channel. If an explicit setting (output level or output destination) is specified, the specification is followed. If no explicit setting is specified, a message is sent to the upper log channel 207.

[Step 4] The log channel 207 that has received the log message, like the log channel 208,
First, it is confirmed whether or not there is an explicit output setting for the own channel. If the output setting has been made, processing is performed according to the setting. On the other hand, the case where the explicit output setting has not been performed, in this case, the log channel 207
Is a root node of a hierarchical structure formed by a log channel under the control of the log controller 203, and reads out default value information set in the log controller 203 and performs processing according to the set value.

<Effects of Specific Example 2> As described above, according to Specific Example 2, in addition to the effects of Specific Example 1, all log output streams existing in the program due to the hierarchical structure of the log channels are logged. It is managed by a tree structure with a manager at the top, and a log controller that allows setting of default values to each module has been introduced. With this configuration, it is possible to form a log output structure that reflects the logical structure of a program between modules and within a module. As a result, the log setting can be performed in an intuitive expression, so that the burden on the log setting of the operation manager can be significantly reduced.

Even for a program in which a plurality of modules are complicatedly related to each other through inheritance, aggregation, and the like, in order to use the setting for a node existing at a higher level in the tree structure as default value information for a lower node, Operation management can be reduced. For example, by changing the setting of the log controller located at the node at the top of a certain module, the setting for the entire module can be performed collectively. Conversely, when it is desired to output only a specific lower stream, it is possible to easily output only the stream by suppressing the output to another stream in the upper node.

According to the above-described invention, the log message is output to a file as an output destination. However, the log message is output to a terminal on a computer or a server on a network for receiving a log message. It may be. In addition, two types of information managed by the log channel, that is, output level and output destination information, have been described. In addition, information such as a comment for indicating information about each channel to the operation manager may be added. .

[0051]

According to the present invention, log management means for managing only one log mechanism existing in a program, output means for writing a log message by the program, and output for judging whether or not the log message output to the output means can be output. By providing the control means and connecting the output control means to the output means or a higher-level output control means, all the output control means are connected to a tree structure having the log management means at the top. The output of the log information can be controlled without changing the program configured by the group.

[Brief description of the drawings]

FIG. 1 is a program configuration diagram for describing a first embodiment of a log output information management system of the present invention.

FIG. 2 is a program configuration diagram for explaining a log output information management system according to a second embodiment of the present invention;

[Explanation of symbols]

 101 log manager 102 first module 103, 106 log channel 104 output stream 105 second module 107 output stream group 108 management client 201 log manager 202 first module 203 log controller 204, 207, 208, 210 log channel 205 output Stream group 206 second module 209,211 output stream

Claims (3)

[Claims] 1. A log output information management system for managing log message information generated in a process of executing a program constituted by a plurality of modules, wherein the log management manages a single log mechanism existing in the program. Means, at least one output means for a program to write a log message, and output control means for determining whether or not the log message output to the output means can be output, wherein the output control means comprises the output means or By connecting to the higher-level output control means, all output control means
A log output information management system, wherein the log management means is connected to a tree structure having vertices. 2. In the determination of the output control means, if an explicit output setting has been performed on the output control means, the output control means must follow it. 2. The log output information management system according to claim 1, wherein the determination is delegated to an output control unit. 3. The method according to claim 2, wherein, when an explicit output setting is not performed on the higher-level output control means, the determination is delegated to a higher-level output control means which is a root node of the tree structure. The log output information management system according to claim 2.