JPH07248943A - Log record management device - Google Patents

Abstract

PURPOSE:To switch a log on and off at an optional point of time during collection of logs and to evade the decceleration of the processing speed of target processes even if the logs are collected by operating a log collection device under processes different from the target processes. CONSTITUTION:A command information output part 4 sends command information to the respective target processes 5 and 6 and a log information collection part. The log information collection part outputs the command information received from the command information output part 4 to an output log file by utilizing the free time of the target processes 5 and 6. Also, log information received from a log information output part 7 is outputted to the output log file by utilizing the free time of the target processes 5 and 6. In such a manner, since the target processes and the log collection device are operated respectively in the different processes and output to the log file is performed by utilizing the free time of a target process processing, even when log output is performed, the processing speed of the target processes is not deccelerated so much compared to the case of performing the log output.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a log recording management system under a multi-process environment.

[0002]

2. Description of the Related Art Outputting the contents of data and the execution status of a program to a log file during execution of the program has been conventionally performed. For example, JP-A-3-
Japanese Patent Publication No. 3046 discloses a method of recording communication data information in a log file in database transaction processing. At the time of program development, log collection is effective for detecting and correcting failures and confirming operation (first method).

Further, Japanese Patent Laid-Open No. 5-61732 discloses a method in which the execution speed does not change much compared to the case where the logs are not collected (second method).

Further, if the target process is executed for a long time while the log is output, the amount of the log will be huge. Therefore, it is difficult to know which part of the log file corresponds to which operation of the user. Further, for example, when a failure of the target process is corrected, it may be desired to perform the exact same operation as described above, log, and compare the contents. At this time, if the content of the input operation is complicated, it is difficult to reproduce the same operation repeatedly. Therefore, it is desirable to automate the reproduction of input operations for the target process. As a method to automatically operate the target process and test,
For example, it is disclosed in Japanese Patent Laid-Open No. 5-61710 (third method).

[0005]

However, in the first method of such log recording management method, by collecting the logs, it takes a long time to output the log file and the execution speed of the target process decreases. I will end up. Also, in order to switch logging on / off, the source program must be recompiled and linked again. For these reasons, there was a problem that it was difficult to collect logs.

In the second method, each library linked to the target process directly outputs the log to a file. For this reason, the more frequently the log is output, the more frequently the file is output, which makes it difficult to effectively use the free time of the target process, and a means for switching the log on / off for each process is provided. There was a problem such as no.

Further, in the third method, it is necessary to separately prepare the data of the input operation for the target process. The creation of this data is done separately from the operation of the target process. Therefore, there is a problem that it is difficult to deal with failures that occur when the target process is actually used.

The present invention has been made in view of the above problems, and by setting the log collecting device as a process different from the target process, the log is switched on / off at an arbitrary point during log collection. In addition, the purpose is to avoid a decrease in the processing speed of the target process even if logs are collected.

Further, the input operation to the target process is saved together with the log information, and the target process is automatically re-executed based on this, thereby automating the reproduction of the fault and the confirmation of the correction, which leads to the development and maintenance. The purpose is to improve efficiency.

[0010]

In order to achieve the above object, the present invention operates in a process different from a target process in a log recording management apparatus that collects logs of one or a plurality of target processes under a multi-process environment. Then
It collects logs by using the free time of processing of the target process.

Further, it is preferable that the log output library linked to the target process detects the activity of the device for collecting the log and switches the log collection on / off based on the detection result.

The target process may be selected at any point during log collection.

Furthermore, it is more preferable to save the user's input operation to the target process together with the log information.

Furthermore, it is more preferable that the stored information is read out, given to the target process, and the target process is re-executed.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be specifically described below with reference to the drawings. FIG. 1 is an example of a block diagram of the present invention. Reference numeral 1 denotes an input unit, and all information of the keys, mouse, etc. input here is passed to the command information output unit 4. An input log file 2 is used as a command input source instead of the input unit 1. The input log file 2 is for automatically executing the target processes 5 and 6. An input source selection unit 3 is for selecting either the input unit 1 as the command input source or the input log file 2. A command information output unit 4 acquires a command for operating the target processes 5 and 6 from the input unit 1 or the input log file 2 and outputs the command to an appropriate target process 5 and 6 and the log information collection unit 10.
It is for sending to.

Reference numeral 7 is a log information output unit, which is connected to the target processes 5 and 6 as a library. The log information output unit 7 is for receiving log commands from the target processes 5 and 6 to create log information, storing the log information in the shared memory 8, and sending a message to the log information collecting unit 10. However, if the log collection device is not active at this time, neither log information is created nor messages are sent. The shared memory 8 is a memory space that can be shared between processes. Reference numeral 9 denotes a log collection device detection unit for detecting whether or not the log collection device is currently active. 1
Reference numeral 0 is a log information collecting unit, which collects log information and command information and outputs them to the output log file 12. Reference numeral 11 is a target process selection unit, which sets the target processes 5 and 6 to be output to the output log file as 1
Or, select multiple items. An output log file 12 stores the log information and command information of each target process 5 and 6. By using the result of the output log file again as the input log file 2, the target processes 5 and 6 are automatically executed.

Next, FIG. 2 shows an example of a flow chart showing the overall flow of the present invention. (A) is a log collection device 13,
(B) shows the processes of the target processes 5, 6, and the log output library 14, respectively. In S21, the type of message acquired by the log collection device 13 is checked, and depending on the type, command output processing (S22),
The process branches to the command information collection process (S23) or the log information collection process (S24). In S22,
The command information output section is processed. Then, the command information is sent to each of the target processes 5 and 6 and the log information collecting unit 1.
Send to 0. In S23 and S24, the process of the log information collecting unit is performed. In S23, the command information output unit 4
The command information received from is output to the output log file 12 using the free time of the target processes 5 and 6. In S24, the log information received from the log information output unit 7 is output to the output log file 12 using the free time of the target processes 5 and 6.

In S25, the processes of the target processes 5 and 6 are performed. In S26, it is checked whether or not the log output instruction is executed in the target processes 5 and 6. In S27 and S28, the process of the log information output unit 7 is performed. In S27, the log output command is received, log information is created, and this is sent to the log information collection unit 10. In S28, it is checked whether or not the processing of the target process cells 5 and 6 is free. If the processing is idle, the control of the CPU is passed to the log collection device 13 side. If not, the process is immediately returned to the target processes 5 and 6.

Next, FIG. 3 shows an example of a flow chart showing the processing of the process switching processing section of the log information output section 7. When the log output command is executed in the target processes 5 and 6, the log information output unit 7 creates log information and sends it to the log management device 13 side. At this time, in S31, it is checked whether the shared memory 8 is full. Here, if the shared memory 8 is full, the log information collection unit 10 is sent to the CP in S32.
Pass control of U. As a result, the log information in the shared memory 8 is output to the output log file 12. Here, if the shared memory 8 is not full, it is checked in S33 whether there is an input message to the target processes 5 and 6. If there is a message, in order to give priority to the processing of the target processes 5 and 6, in S34,
The control to the target processes 5 and 6 is returned, and the processing of the log information output unit 7 ends.

Next, an example of a flow chart showing the processing of the log information output unit 7 is shown in FIG. When the log output command is executed in the target processes 5 and 6, the log information output unit 7 is called. Then, in S41, the log collection device detection unit 9 is called. Next, in S42, it is detected whether the log collection device 13 is active. If the log collecting apparatus 13 is active, the log information output unit 7 creates log information in S43. The created log information is stored in the shared memory 8 in S44. Then, in S45, a message representing the log information is sent to the log information collection unit 10.

In S42, if the log collecting apparatus 13 is not active, the process from S43 to S45 is not performed, and control is immediately returned to the target processes 5 and 6.

Next, an example of a flow chart showing the processing of the log information collecting unit 10 is shown in FIG. First, in S51, a message from the log information output unit 7 is received. Next, S
At 52, the presence or absence of a message is checked. If there is a message, the log information is acquired and output to the output log file 12. In step S53, the target process selecting unit 11 obtains the log output target process among the log output target processes 5 and 6. In S54, it is checked whether the target process of the message transmission source has been selected by the target process selection unit 11. Here, if selected, S5
5, the log information is acquired from the shared memory 8 and S5
In 6, the log information is output to the output log file 12. Then, in S57, the log information is discarded and the process ends.

If a message is received from the target process not selected by the target process selection unit 11 in S54, the output log file 12
Is not output to, and the log information is discarded as it is (S
57).

An example of log information in the shared memory 8 and the output log file 12 is shown in FIG. The log information is composed of three parts: a symbol 61 representing the log information, a target ID 62, and a log content 63 passed from the log output command.

Next, FIG. 7 shows an example of a flow chart showing a process of collecting command information in the log information collecting unit 10.
First, in S71, a message is received from the command information output unit 4. The message received here is an operation such as a mouse, a key, or a menu selection that the user has input to the target processes 5 and 6. Next, S72
At, check for the presence of a message. If there is a message, the command information is output to the output log file 12 in S74. Then, in S75,
Discard the command information and terminate. In S72,
If there is no message, the process ends as it is.

FIG. 8 shows an example of command information in the output log file 12. The command information consists of four parts: a symbol 81 indicating the command information, a target ID 82, a message 83 indicating the type of command, and a parameter value 84.

Next, FIG. 7 shows an example of a flow chart showing the process of command information output in the command information output unit 4. First, in S91, the target processes 5, 6
Determine the input source of the message that causes the. Either the input unit 1 or the input log file 2 can be selected as the input source. In S92, the input destination is the input unit 1
And the input log file 2 are checked. If the input destination is the input unit 1, the message is received from the input unit 1 in S93. On the other hand, when the input destination is the input log file 2, command information is read from the input log file 2 in S94, and then S
At 95, a message is created from the read command information.

Next, in S96, the message destination target n is determined. The destination is the target process that is currently interacting with the user when the input source is the input unit 1, and the target ID 8 recorded in the command information when the input source is the input log file 2.
2 is the target process. After determining the destination process of the message, the message is sent to the determined target process in S97.
This allows the target process to actually run. Further, in S98, the message having the same content is also sent to the log information collecting unit 10. As a result, the command information is recorded in the output log file 12.

As described above, according to the log management apparatus of the present invention, the target process and the log collection apparatus operate in separate processes, and the log file is written to the log file by utilizing the idle time of the target process processing. As a result, the processing speed of the target process does not decrease so much even if the log is output, compared to the case where the log is not output. Also, the log information of multiple target processes can be output to a log file all at once. In addition, log information can be collected on other machines via the network. Even in this case, the load on the CPU on the target process execution side is reduced, so that the speed decrease of the target process can be further reduced. Further, according to the log management device of the present invention, the log output library detects the activity of the log collecting device and does not output the log information if the log collecting device is not active, so that the target process is changed / compiled / linked. Log collection can be turned on / off at any point during execution of the target process without re-execution. Further, when the log collection is not performed, the decrease in the speed of the target process can be greatly reduced. Further, according to the log management device of the present invention, the target process to be output to the log file is
Since one or more can be selected, only the log information of the necessary process can be collected when many target processes are operating. Also, since this selection is made on the log collection device side, the target process can be selected at any point during log collection. Further, according to the log management device of the present invention, the user's input operation is also output to the log file together with the log information output by the target process. Therefore, command information indicating the user's input operation is included in the log file. , The log information corresponding to the input operation is written alternately, and the user can easily analyze the log file. Further, according to the log management apparatus of the present invention, one or a plurality of target processes can be automatically re-executed by reading the command information output to the log file and supplying it to the target process again. , If a failure occurs in the target process due to a series of operations, the command information and log information are saved, and the target process is automatically executed using this, and the failure reproduction test is automatically performed. be able to. When the target process is modified, the target process before and after the modification is automatically executed and the output log files are compared, so that the modification result can be easily confirmed.

[Brief description of drawings]

FIG. 1 is an example of a functional block diagram showing an outline of a log recording management device according to the present invention.

FIG. 2 is an example of a flowchart showing the overall processing procedure of the log recording management apparatus according to the present invention.

FIG. 3 is an example of a flow chart showing processing of a process switching processing unit of the log recording management apparatus according to the present invention.

FIG. 4 is an example of a flowchart showing a process of a log information output unit of the log recording management device according to the present invention.

FIG. 5 is an example of a flow diagram showing a process of a log information collecting unit of the log recording management apparatus according to the present invention.

FIG. 6 is an example of log information in a shared memory and an output log file of the log recording management device according to the present invention.

FIG. 7 is an example of a flowchart showing a command information collecting process of the log recording management apparatus according to the present invention.

FIG. 8 is an example of command information in an output log file of the log recording management device according to the present invention.

FIG. 9 is an example of a flowchart showing a command information output process in the log recording management apparatus according to the present invention.

[Explanation of symbols]

 1 Input Section 2 Input Log File 3 Input Source Selection Section 4 Command Information Output Section 5 Target 1 6 Target n 7 Log Information Output Section 8 Shared Memory 9 Log Collection Device Detection Section 10 Log Information Collection Section 11 Target Selection Section 12 Output Log File 13 Log collector 14 Log output library

Claims (5)

[Claims] 1. A log recording management device for collecting logs of one or a plurality of target processes under a multi-process environment, the process operating as a process different from the target process, and using the idle time of the processing of the target process. A log recording management device characterized by collecting the logs. 2. In a log recording management device for collecting logs of one or a plurality of target processes under a multi-process environment, a log output library linked to the target process performs an activity of the device for collecting the logs. A log recording management device characterized by detecting and switching on / off of collection of the log based on the detection result. 3. A log recording management apparatus for collecting logs of one or a plurality of target processes in a multi-process environment, wherein the target process is selected at an arbitrary point during the log collection. Management device. 4. A log recording management device for collecting logs of one or a plurality of target processes under a multi-process environment, characterized in that a user's input operation to the target process is stored together with the information of the log. Log record management device. 5. The log recording management device according to claim 4,
A log recording management device, wherein the stored information is read out, given to the target process, and the target process is re-executed.