JP2010066801A - Log recording system, module monitoring means, trace log managing means, recording method, program, and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a log recording system, a module monitoring means, a trace log managing means, a recording method, a program, and a storage medium that improve a problem place detection rate when problem arising after product shipment of software on a communication system. <P>SOLUTION: The log recording system includes, for a plurality of modules, a module monitoring means of periodically making a health check and a trace log managing means of receiving log recording requests from the respective modules and recording logs in a plurality of trace files. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a log recording system, module monitoring means, trace log management means, recording method, program, and storage medium.

In program development, logs are embedded for unit tests and combination tests, but the logs are often left as logs that are not output after product shipment, but are not normally used.
On the other hand, when problems occur after shipment, in order to keep the log output to the minimum necessary in consideration of the log output disk capacity, create a mechanism to record the necessary logs when passing the abnormal route on the program Yes.

However, there are cases where it is difficult to identify a problem location with such a log alone, and there is a need to provide a means for confirming a log at a unit / combination test level.
Therefore, Patent Document 1 describes a function of detecting a program abnormality by performing a health check and restarting the program.
Further, techniques related to Patent Document 1 are described in Patent Documents 2 and 3.
The “software system” of Patent Document 1 detects a health check command that is sent when an application program operates normally in a software system that includes an OS (Operation System) and an application program that runs on the OS. The monitoring program for forcibly terminating the application program when the health check command is not detected is configured on the OS ”.

  According to the invention described in Patent Document 1, even in a software system in which the OS cannot be modified so as to add a function for monitoring an application program, an abnormality of the application program is detected by the monitoring program, When an abnormality is detected, the application program can be forcibly terminated and restarted (rebooted). As a result, it is possible to provide a highly reliable software system.

  The “system console failure notification method” described in Patent Document 2 is a “method of notifying maintenance personnel of a failure of a system console connected to a computer device” and is periodically provided with a health check message provided in the computer device. Health check message sending means, health check message receiving means provided in the system console for receiving health check messages, and response provided in the system console for sending a response message when the health check message receiving means receives a health check message Failure detection that transmits a warning signal if the response message receiving means provided in the computer device does not receive the response message within a predetermined time. Means and a warning signal provided in the computer device. Upon receiving the one in which "and a warning device which emits a prescribed warning.

  According to the invention described in Patent Literature 2, the response of the system console to the health check message is monitored on the computer device side, and if the response message is not obtained within a predetermined time, it is determined that the system console has failed, and is provided in the computer device. In order to operate the alarm device, the maintenance staff can be notified immediately of the system console failure.

  The method for dynamically changing the log level of an application described in Patent Document 3 describes a function for internally setting a log level as an output standard by reading an external log level setting table, and logging at key program points. When an output statement is written with a level and this log output statement is encountered during program execution, this log is output to an external log file when this level is below the log level set internally as the output standard. And a function to re-read the log level setting table and change the internal setting of the log level as an output standard when receiving a log level change notification from the outside. The application process that starts under management and the execution status of the application process can be queried from the kernel Therefore, when an application process is started as its own child process and a failure occurs in the application process by this query that is performed at a predetermined cycle during execution, the application in the log level setting table is detected. The log level as the output standard is rewritten to a high level, and an application defect detection process for transmitting a signal for notifying the application process of the log level change is executed.

According to the invention described in Patent Document 3, when an application that outputs a log file according to a log level is executed, the log level is dynamically changed as necessary. Logs necessary for investigating the cause of an application trouble can be sufficiently written to the log file without causing the problem of compression of free space on the hard disk or the like by the log file. This is a particularly useful method when the log file tends to be enlarged because it is continuously executed over a long period of time, such as an application executed in a monitoring control system that is continuously operated 24 hours a day. .
JP 2003-173274 A JP-A-10-116211 JP 11-327965 A

  The log recording system related to the present invention has a mechanism for recording the state at that time as a log when an abnormality is detected, except for communication recording for billing etc. Incorporated. For example, it provides a mechanism for leaving a log indicating that there is an abnormality when passing through an abnormal route on the program. However, there are cases where it is difficult to identify the problem part only with such a log.

  On the other hand, if the debug logs at the unit test and integration test levels are frequently recorded even during normal operation, analysis at the time of the problem will be easier, but the debug logs at the unit test and integration test levels will be output at the time of shipment. If it continues, there is a problem that memory capacity is depleted and troubles such as inability to record important information occur.

  Accordingly, an object of the present invention is to provide a log recording system, a module monitoring unit, a trace log management unit, a recording method, a program, and a program that improve a problem location detection rate when a problem occurs after product shipment in software on a communication system. And a storage medium.

  The system of the present invention includes a module monitoring unit that periodically performs a health check for a plurality of modules, a trace log management unit that receives a log recording request from each module and records the logs in a plurality of trace files, It is provided with.

  The module monitoring means of the present invention receives a log recording request from each module, and the module monitoring means used in the log recording system provided with the trace log management means for recording the log in a plurality of trace files includes a plurality of modules. On the other hand, the health check is performed periodically, and the health check is performed periodically for a plurality of modules.

  The trace log management means of the present invention receives a log recording request from each module in a trace log management means used in a log recording system provided with a module monitoring means for periodically performing a health check on a plurality of modules. The log is recorded in a plurality of trace files.

  The log recording method of the present invention is characterized by periodically performing a health check on a plurality of modules, receiving a log recording request from each module, and recording the logs in a plurality of trace files.

  The program of the present invention is a computer-readable program, in which the computer periodically performs a health check on a plurality of modules in the module monitoring means, and log recording from each module in the trace log management means A procedure for receiving a request and recording a log in a plurality of trace files is executed.

  The storage medium of the present invention stores the above program.

  According to the present invention, a log recording system, module monitoring means, trace log management means, recording method, program, and storage with improved problem location detection rate when a problem occurs after product shipment in software on a communication system Provision of a medium can be realized.

<Features>
FIG. 1 is a conceptual diagram showing an embodiment of a log recording system according to the present invention.
An embodiment of the log recording system according to the present invention is configured such that the module monitoring unit 13 that performs the health check of each module 11 and the trace log management unit 12 detect the timeout of the health check of the module having the module monitoring unit 13. The unit 18 for notifying that the health check timeout has occurred and the unit 16 for recording by changing the log recording setting level of the module for which the health check has timed out by the trace log management unit 12 are detected. , Characterized in that it operates to record a log of the binding test level.

<Configuration>
Next, the configuration of an embodiment of a log recording system according to the present invention will be described in detail with reference to the drawings.
Referring to FIG. 1, the log recording system includes a plurality of modules 11 (module A to module X), a trace log management unit 12, a module monitoring unit 13, and a plurality of trace log files 14 (trace log files A to And a trace log file X).

  The module 11 is composed of a plurality of modules, and is a module group for providing various functions of the communication system. Each module 11 includes means 15 for making a log recording request to the trace log management unit 12 and means 17 for returning a response to the health check from the module monitoring unit 13.

  The trace log management unit 12 has a function of receiving a log recording request 15 from each module 11 and receiving a log 16 and a health check timeout notification 18 from the module monitoring unit 13.

  The module monitoring unit 13 includes means 17 for periodically performing a health check on each module 11. Also. A function of transmitting a health check timeout notification 18 to the trace log management unit 12 when a health check response cannot be received from each module 11 within a predetermined time is provided.

  The trace log file 14 is a file for recording a log in module units, and the log is written by the trace log management unit 12.

<Description of operation>
Next, the operation of the present embodiment will be described in detail with reference to FIG. 1, FIG. 2, FIG. 3, and FIG.
First, the operation of the module monitoring unit 13 will be described with reference to FIG.
FIG. 2 is an example of a flowchart for explaining the operation of the module monitoring unit used in the log recording system shown in FIG.
The module monitoring unit 13 periodically performs a health check on each module 11, and there is a state in which a health check response can be received from each module 11 within a predetermined time (step 31).

  When a health check response cannot be transmitted due to a failure of a certain module (here, module A) from the state in which the health check response can be received, the health check response waiting timer of the module monitoring unit 13 is set. By timeout, the health check timeout of module A is detected (step S32), and the first time is counted as the first time. (Step 32 / Yes).

Next, a health check timeout detection notification of module A is transmitted to the trace log management unit (step 33).
Also in the next periodic health check, a health check timeout is detected (step 34), and in the second case, it is counted as the second time (step 34 / Yes).

  In this way, the number of health check timeouts is counted up, and it is determined whether or not the count value N until the set restart is reached (step 35). When the count value N is reached (step 35 / Yes) Then, the apparatus is restarted (step 36).

  If the health check response of module A is received while the count count of the health check timeout is less than N (step 32 / No, step 33 / No, step 34 / No, step 35 / No), module A is restored. And a recovery notification is sent to the trace log management unit (step 37), and the normal operation is resumed (step 31).

Next, the log recording level of the trace log management unit 12 will be described with reference to FIG.
FIG. 3 shows an example of the log recording level of the trace log management unit used in the log recording system shown in FIG.
When each module makes a log recording request to the trace log management unit, the log recording level is included in the parameter and transmitted.
In FIG. 3, the level is divided into 8 levels. In the initial setting, the log recording setting level is set for each module.
The trace log management unit 12 determines whether or not to write the received log recording request to a file based on the setting information. For example, when the log recording setting level of module A is set to error (hereinafter referred to as error), the trace log management unit has a log recording level with a priority of error or higher among log recording requests received from module A. Only log parameter requests are recorded, and log recording requests with a priority lower than error are not written to a file.

The operation of the trace log management unit 12 will be described with reference to FIG.
FIG. 4 is an example of a flowchart for explaining the operation of the trace log management unit used in the log recording system shown in FIG.
A log recording request is received from each module 11. Here, a case where a log recording request from module A is received will be described.
When a log recording request is received from module A (step 41), the log recording level of module A is confirmed. That is, it is determined whether the reception level ≧ the set level (step 42).
The log recording level of the received log recording request is compared with the log recording setting level of module A. When the priority is higher than or equal to the log recording setting level (step 42 / Yes), file output is performed (step 42). 43). Otherwise, that is, when the priority is lower than the log recording setting level (step 42 / No), the next log recording request is received without outputting the file (step 41).

On the other hand, the trace log management unit 12 waits for receiving a message from the module monitoring unit 13 (step 44).
When the health check timeout detection notification of module A is received from the module monitoring unit 13 (step 45), the log recording setting level of module A is lowered. The level to be lowered can be changed by setting, and here, the debug mode is lowered to the lowest priority (step 46).
Thus, all log files of module A are output from the reception of the next log recording request.
Similarly, when a health check timeout recovery notification of module A is received from the module monitoring unit 13 (step 45), the log recording setting level of module A is restored (step 46).

  As described above, in this embodiment, there is a mechanism for changing the log recording level when a module abnormality is detected, so that a log can be recorded at the unit test and the combined test level when the abnormality is detected.

<Description of effects>
According to the present embodiment, problem analysis when a module abnormality occurs can be performed at the unit test level and the combined test level.
The reason is that when a health check timeout occurs, the log recording level of the module is lowered and recorded.

<Program and storage medium>
The log recording system of the present invention described above is realized by a program that causes a computer to execute processing. Examples of the computer include general-purpose computers such as personal computers and workstations, but the present invention is not limited to this.

In other words, this program
A computer-readable program,
Computer
(1) Procedure for regularly checking the health of multiple modules in the module monitoring means,
(2) The trace log management means receives a log recording request from each module, and causes the log to be recorded in a plurality of trace files.

In addition to the above configuration, the computer
(3) The module monitoring unit may be caused to execute a procedure for notifying the health check timeout.

In addition to the above configuration, the computer
(4) The module monitoring means restarts when the number of health check timeouts reaches the specified number.If the health check response is received while the number of health check timeouts is less than the specified number, the trace log management means You may perform the procedure which performs recovery notification.

In addition to the above configuration, the computer
(5) The module monitoring means may be caused to execute a procedure in which each module sends a log recording level as a parameter when each module makes a log recording request to the trace log management means.

In addition to the above configuration, the computer
(6) The trace log management unit may execute a procedure for receiving a health check timeout notification from the module monitoring unit.

Thus, the system of the present invention can be realized anywhere as long as there is a computer environment capable of executing the program.
Such a program may be stored in a computer-readable storage medium.
Here, examples of the storage medium include a computer-readable storage medium flash memory such as a CD-ROM (Compact Disc Read Only Memory), a flexible disk (FD), and a CD-R (CD Recordable), and a RAM (Random Access). Memory, ROM (Read Only Memory), semiconductor memory such as FeRAM (ferroelectric memory), and HDD (Hard Disc Drive).

  The above-described embodiment shows an example of a preferred embodiment of the present invention, and the present invention is not limited thereto, and various modifications can be made without departing from the scope of the invention. is there.

<Others>
Here, differences between the present embodiment and Patent Documents 2 and 3 will be described.
The invention described in Patent Document 2 discloses an abnormality detection means, but this abnormality detection means is outside the scope of the present invention, and is an example of a trigger function for explaining the mechanism of changing the log recording level. It is only mentioned as.
The invention of the present application differs from the invention described in Patent Document 2 in the implementation method of the log level changing method.

  In the invention described in Patent Document 3, when an abnormality is detected, the log level of the log level setting table is changed, each module reads the table, and each module changes the log level and leaves a log.

  On the other hand, the present invention unifies trace log recording processing. For this reason, each module does not need to be aware of the log recording level, and it is easy to add and remodel modules, thereby improving productivity and maintainability.

In the invention described in Patent Document 3, each module receives a log level change notification, and the process of actual change is left to each application. Therefore, the change timing varies from module to module, and the log level changes. Cannot synchronize. Furthermore, although the processing is congested, the log level change timing of the module is greatly delayed, and there is a possibility that a necessary log may be missed.
In general, the congestion module often includes a problem, and in such a case, the invention described in Patent Document 3 is less likely to leave a useful log.

  On the other hand, the present invention makes it easy to change the log level of a congested module, synchronize the log level change, and further improve the ease of analysis. Moreover, productivity and maintainability can be improved by performing unified management.

  INDUSTRIAL APPLICABILITY The present invention can be applied to software having a health check function in embedded development with strict memory restrictions and a system having a mechanism for determining the presence / absence of file output according to a log recording level and a system using the software.

It is a conceptual diagram which shows one Embodiment of the log recording system which concerns on this invention. It is an example of the flowchart for demonstrating operation | movement of the module monitoring part used for the log recording system shown in FIG. It is an example of the log recording level of the trace log management part used for the log recording system shown in FIG. It is an example of the flowchart for demonstrating operation | movement of the trace log management part used for the log recording system shown in FIG.

Explanation of symbols

11 modules (module A to module X)
12 Trace log management unit 13 Module monitoring unit 14 Trace log file (trace log file A to trace log file X)

Claims (20)

Module monitoring means to periodically check the health of multiple modules,
A log recording system comprising: a trace log management unit that receives a log recording request from each module and records the log in a plurality of trace files.   The log recording system according to claim 1, wherein the module monitoring unit issues a health check timeout notification.   The module monitoring unit restarts when the number of health check timeouts reaches a predetermined number, and recovers to the trace log management unit when a health check response is received while the number of health check timeouts is less than the predetermined number The log recording system according to claim 2, wherein notification is performed.   3. The log recording system according to claim 2, wherein the module monitoring unit transmits a log recording level including a parameter when each module makes a log recording request to the trace log management unit.   The log recording system according to claim 2, wherein the trace log management unit receives a health check timeout notification from the module monitoring unit. In the module monitoring means used in the log recording system provided with the trace log management means for receiving the log recording request from each module and recording the log in a plurality of trace files,
A module monitoring unit characterized in that a health check is periodically performed on a plurality of modules, and a health check is periodically performed on the plurality of modules.   7. The module monitoring unit according to claim 6, wherein the module monitoring unit performs a health check timeout notification.   The module monitoring unit restarts when the number of health check timeouts reaches a predetermined number, and recovers to the trace log management unit when a health check response is received while the number of health check timeouts is less than the predetermined number The module monitoring means according to claim 7, wherein notification is performed.   8. The module monitoring unit according to claim 7, wherein when each module makes a log recording request to the trace log management unit, the module monitoring unit includes a log recording level as a parameter.   Trace log management means used in a log recording system equipped with a module monitoring means that periodically performs health checks on multiple modules, receives log recording requests from each module, and records logs in multiple trace files Trace log management means characterized by:   The trace log management means according to claim 10, wherein the trace log management means receives a health check timeout notification from the module monitoring means. Regular health checks on multiple modules,
A log recording method comprising receiving a log recording request from each module and recording the log in a plurality of trace files.   13. The system is restarted when the number of health check timeouts reaches a predetermined number, and a recovery notification is performed when a health check response is received while the number of health check timeouts is less than the predetermined number. Logging method.   13. The log recording method according to claim 12, wherein when each module makes a log recording request, the log recording level is included in a parameter and transmitted. A computer-readable program,
The computer is
Procedure to regularly check the health of multiple modules in the module monitoring means,
A program that causes a trace log management means to receive a log recording request from each module and to execute a procedure for recording logs in a plurality of trace files.   16. The program according to claim 15, wherein the computer causes the module monitoring unit to execute a procedure for performing a health check timeout notification.   If the computer restarts the module monitoring means when the number of health check timeouts reaches a predetermined number, and receives a health check response while the number of health check timeouts is less than the predetermined number, the trace log 16. The program according to claim 15, wherein the management unit is caused to execute a procedure for performing a recovery notification.   17. The computer according to claim 16, wherein the computer causes the module monitoring unit to execute a procedure of transmitting a log recording level as a parameter when each module makes a log recording request to the trace log management unit. program.   The program according to claim 16, wherein the computer causes the trace log management unit to execute a procedure of receiving a health check timeout notification from the module monitoring unit.   A storage medium storing the program according to any one of claims 15 to 19.

Images