JP2007058265A - Log output controller and log output control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a log information output controller capable of efficiently recording and managing log information by outputting only log information needed to decide fault contents etc., to a file device when a fault occurs to an application program. <P>SOLUTION: A log output control program 120 includes: respective processing means which are an internal information receiving means 121, a detailed log information generating means 122, a detailed log information storage means 123, a program error information receiving means 124, a fault log information generating means 125, a detailed log output request means 126, a log message generating means 127, and a log message output means 128; and a detailed log information holding area 129 as a temporary storage area. The detailed log output means 126 outputs detailed log information stored in the detailed log information holding area 129 as information to be stored in a log storage means 130 within specified ranges right before and right after the timing of reception of program error information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a log information output control device and program related to an application program in a computer system or the like.

2. Description of the Related Art Conventionally, a process of storing internal information of an application program itself as log information in a file device is generally performed for the purpose of providing a failure content and a determination method of a solution method when a failure occurs in the application program.
In this case, by outputting as detailed internal information as possible as log information, it is possible to provide useful data for determining the content of the failure and the solution.
In other words, it is highly possible that the internal information before the occurrence of the failure is the information that caused the failure, and the internal information after the occurrence of the failure also determines whether the error handling for the occurred failure is performed correctly. Therefore, it becomes easier to judge the content of the obstacle and the solution method.
For example, when a failure occurs as a trigger and another failure occurs in the subsequent process, the failure that occurred later occurred first by checking whether the error handling of the failure that occurred earlier was performed correctly It is possible to determine whether or not the error is due to faulty error handling.

On the other hand, the more detailed the internal information that is output as log information, the larger the amount of data, so the period until the capacity of the file device that records the log information becomes full is shortened, and the failure is determined. -There was a high possibility that effective log information could not be saved for resolution.
In this regard, as a conventional log information storage method, the log information output by the host system is written to the file device, the number of output log information is measured, and the log information is written to the file device when the number exceeds the threshold. It is well known that the log information is read again, the importance of the log information is judged, only the log information with high importance is written again to the file device, and the log information with low importance is written to the file device as statistical information. (For example, refer to Patent Document 1).
Japanese Patent Laid-Open No. 10-275098

However, the configuration described in Patent Document 1 has a problem that the criteria for determining the importance of log information is not clear, and it is not always possible to record log information necessary for determining the content of a failure or a solution. .
In addition, since the number of log information increases, the writing process to the file device also increases, so that more computer resources are consumed. Therefore, as in Patent Document 1, in addition to normal log information writing, when rereading or writing back for importance determination is performed, more computer resources are consumed, and the application program itself There was a risk of performance degradation.

  SUMMARY OF THE INVENTION The present invention is to solve the above-mentioned problem, and as an output control device for log information of an application program, only a log information necessary for discriminating the content of the failure when a failure of the application program occurs is a file device. It is an object of the present invention to provide a log information output control device that enables log information to be recorded and managed efficiently.

In order to solve the above problems, the log output control device of the present invention is a log output control device that generates a log message based on internal information output from an application program and program error information and stores the log message in the storage device. Means for storing internal information in a temporary storage area, means for acquiring internal information in an arbitrary range based on the reception time of the program error information from the temporary storage area, and generating the log message; Means for storing a log message in the storage device.
The internal information in the arbitrary range indicates a predetermined number of internal information before and after the internal information stored when the program error information is received.
Further, the internal information in the arbitrary range indicates internal information stored within a predetermined time before and after the time when the program error information is received.
The log output control program of the present invention is a log output control program for causing a computer to execute a process of generating a log message and storing it in a storage device based on internal information output from an application program and program error information. , Storing the internal information in the temporary storage area, and acquiring the internal information stored in an arbitrary range based on the reception time of the program error information from the temporary storage area, and generating the log message The computer is caused to execute processing and processing for storing the generated log message in the storage device.
The internal information in the arbitrary range indicates a predetermined number of internal information before and after the internal information stored when the program error information is received.
Further, the internal information in the arbitrary range indicates internal information stored within a predetermined time before and after the time when the program error information is received.

  With the above configuration, in the present invention, when an application program failure occurs, only a fixed number of internal information immediately before and immediately after the instruction that caused the failure or a predetermined period of internal information is output to the file device as detailed log information. As a result, it is possible to efficiently acquire and manage log information that is likely to be a material for determining a failure that has occurred and a method for determining and solving the failure, while suppressing a decrease in performance of the application program itself.

Hereinafter, a log information output control device according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram illustrating a schematic configuration of a computer system including a log information output control device according to the present embodiment.
The computer system according to the present embodiment includes an application program 110 that is an output target of log information, a log output control program 120, and a log storage device 130 that is an output destination of log information.
The application program 110 is a program that operates on a computer system that sequentially executes instructions defined in the application program 110 itself and performs some processing, and an internal information transmission unit 111 as a processing unit corresponding to the log information output program 120. And an error occurrence determination unit 112 and a program error information transmission unit 113.
The internal information transmitting unit 111 transmits internal information such as a variable value at the time of executing an instruction held by the application program 110 to the log output control program 120.
The error occurrence determination unit 112 determines the occurrence of a program error when an instruction of the application program 110 is executed.
The program error information transmission unit 113 transmits information on the generated program error to the log output control program 120 according to the determination result of the error occurrence determination unit 112.
The log output control program 120 includes an internal information receiving means 121, a detailed log information generating means 122, a detailed log information storing means 123, a program error information receiving means 124, a failure log information generating means 125, a detailed log output requesting means 126, a log message. Each processing unit includes a generation unit 127 and a log message output unit 128, and a detailed log information holding area 129 as a temporary storage area.
The internal information receiving unit 121 receives internal information from the internal information transmitting unit 111.
The detailed log information generating unit 122 generates detailed log information based on the internal information received by the internal information receiving unit 121.
The detailed log information storage unit 123 stores the detailed log information generated by the detailed log information generation unit 122 in the detailed log information holding area 129.
The program error information receiving unit 124 receives the program error information transmitted from the program error information transmitting unit 113.
The failure log information generation unit 125 generates failure log information based on the program error information received by the program error information reception unit 124.
The detailed log output means 126 outputs the detailed log information stored in the detailed log holding area 129 in response to the program error information received by the program error information receiving means 124.
The log message generation unit 127 generates a detailed log message and a failure log message based on the detailed log information output from the detailed log information holding area 129 by the detailed log output unit 126 and the failure log information generated by the failure log information generation unit 125. Generate.
The log message output unit 128 outputs the detailed log message and the failure log message generated by the log message generation unit 127 to the log storage device 130.
In this embodiment, the detailed log output unit 126 stores the detailed log information in the detailed log information holding area 129 within a predetermined range (a fixed number or a fixed period) immediately before and after the timing of receiving the program error information by the program error information receiving unit 124. The detailed log information is output as a storage target of the log storage device 130.

Based on the above configuration, processing performed by the log information output control apparatus according to the present embodiment will be described.
FIG. 2 is a diagram showing an instruction group described in Java (“Java” is a registered trademark of Sun Microsystems, Inc.) as an example of the application program 110.
The method 210 is a Java method composed of a plurality of instructions defined in the application program 110, and the application program 110 executes the instructions of the method 210 in order from the top.
The program error determination structure 211 corresponding to the error occurrence determination means 112 is configured by a try clause 212 and a catch clause 213, and the application program 110 generates an exception as a program error in Java when the instruction group 214 in the try clause 212 is executed. When it occurs, control is transferred to the catch clause 213 without executing the subsequent instruction group, and the instruction group 215 in the catch clause 213 is executed. In the instruction group 215 in the catch clause 213, it is possible to access exception information with the program error variable 230 defined in the catch line.
In this example, the error determination unit 111 is realized by the Java try-catch syntax, but it can also be realized by a general control structure of a program such as an if syntax.
Detailed log output commands 216, 217, 218, and 219 corresponding to the internal information transmission unit 111, as indicated by the arguments 231 and 232, are the internal information of the application program 110, the class name as the argument 231 and the message as the argument 232 Can be specified and executed in a character string format. Also, as shown in Expression 233, variables in the program can be specified as an argument 232 by connecting them with a “+” character.
The error occurrence instruction 220 is an instruction that may cause a program error, and a program error occurs when an argument 234 other than a character string (0 to 9) constituting a numerical value is designated.
The failure log output command 221 corresponding to the program error information transmission unit 113 is a command for outputting the exception information and internal information of the application program 110 to the log output control program 120. Similarly to the detailed log output commands 216 to 219, As internal information of the program 110, a class name and a message are specified as a character string as an argument, and a program error variable 230 is specified as an argument as shown by an argument 235, so that exception information can be specified and executed. Is possible.

FIG. 3 is a diagram illustrating an example of the data structure of the detailed log information generated by the detailed log information generating unit 122 based on the internal information of the application program 110.
Detailed log information shown in this example includes data items of a generation time 301, a class name 302, and a message 303.
The generation time 301 indicates the time when the generation processing by the detailed log information generation unit 122 is performed.
The class name 302 is a character string indicating the class name for which the detailed log information output command in the application program 110 has been executed.
A message 303 is a character string representing a message including internal information of the application program 110.

FIG. 4 is a diagram illustrating an example of the data structure of the failure log information generated by the failure log information generation unit 125 based on the program error information of the application program 110.
The failure log information shown in this example has data items of a generation time 401, a class name 402, a message 403, and exception information 404.
The generation time 401 indicates the time when the generation processing by the failure log information generation unit 125 is performed.
The class name is a character string indicating the class name for which the fault log information output command in the application program 110 has been executed.
A message 403 is a character string representing a message including internal information of the application program 110.
The exception information 404 represents details of the exception information that has occurred.

Next, detailed log information storage processing and output processing of the detailed log information holding area 129 in the present embodiment will be described with reference to the images of FIGS.
FIG. 5 is an image diagram showing a storage process of detailed log information in the detailed log information holding area 129.
As shown in FIGS. 5 to 8, the detailed log information holding area 129 is configured with a fixed-length data structure in which the front end and the end of the array are connected to form a ring. This data structure is generally called a ring buffer.
In FIG. 5, reference numeral 501 denotes a registration pointer indicating a detailed log information element serving as a current detailed log information storage position, and reference numerals 502 to 504 indicate registration pointers indicating detailed log information elements serving as past detailed log information storage positions. Reference numeral 505 denotes an arrow indicating the moving direction of the registration pointer 501.
Reference numeral 506 denotes detailed log information stored in the detailed log information element, and reference numeral 507 denotes detailed log information before storage.
Reference numeral 508 denotes a detailed log information element in which detailed log information is not stored, and reference numeral 509 denotes a detailed log information element in which detailed log information is stored.
In this processing, the registration pointer 501 first exists at the position of the registration pointer 503 when the log output control program 120 is activated. The detailed log information storage unit 123 stores the detailed log information 507 in the detailed log information element indicated by the registration pointer 501.
Next, the registration pointer 501 sequentially points to each detail log information element in the direction indicated by the arrow 505 as indicated by the registration pointers 502 to 504 according to the storage of the detail log information 507 by the detail log information storage unit 123. While moving.

FIG. 6 is an image diagram showing an output process of detailed log information when a failure occurs.
In FIG. 6, reference numeral 601 denotes a registration pointer at the time when the detailed log output means 126 makes an output request.
Reference numerals 602 to 605 denote output pointers generated in response to an output request from the detailed log output unit 126, and reference numeral 606 denotes an arrow indicating the moving direction of the output pointer 601.
607 is the detailed log information stored in the detailed log information element indicated by the output pointer 601, and 608 is the output detailed log information.
Reference numeral 609 denotes a failure occurrence pointer indicating the detailed log information element indicated by the registration pointer at the time when the output request is made by the detailed log output means 126, and reference numeral 610 denotes an output pointer that has reached the detailed log information element indicated by the failure occurrence pointer.
In this process, an output pointer 602 and a failure occurrence pointer 609 are generated at the time when an output request is made by the detailed log output means 126, and moves while sequentially pointing each detailed log information element in the direction indicated by the arrow 606.
Next, as indicated by the output pointers 603 to 605, when the detailed log information elements in which the detailed log information 607 is stored are reached, the detailed log information 608 is output in order.
Finally, as shown by the output pointer 610, when each detailed log information element pointed to by the registration pointer 601 is reached, the output process is terminated.

FIG. 7 is an image diagram showing a method of storing detailed log information after a failure occurs.
In FIG. 7, reference numeral 701 denotes a failure occurrence pointer generated when a failure occurs, and reference numerals 702 to 704 denote registration pointers. Reference numeral 705 denotes an arrow indicating the moving direction of the registration pointers 702 to 704. Reference numeral 706 denotes a detailed log information element that is an output target of detailed log information after the occurrence of a failure. Here, the detailed log information element 706 that is the output target of the detailed log information is assumed to have an upper limit set in advance, and in this example, the upper limit is set to “4”.
In this processing, as indicated by the registration pointers 702 to 704, the detailed log information is stored in the detailed log information element 706 in the direction of the arrow 705 in order from the detailed log information element indicated by the failure occurrence pointer 701.

FIG. 8 is an image diagram showing a method for outputting detailed log information after the occurrence of a failure.
In FIG. 8, 801 indicates a failure occurrence pointer generated when a failure occurs, and 802 indicates an arrow indicating the movement direction of the failure occurrence pointer 801. Reference numeral 803 denotes a registration pointer. Reference numeral 804 denotes a detailed log information element that is an output target of detailed log information after the occurrence of a failure. Reference numeral 805 denotes detailed log information to be output.
In this processing, when the detailed log information is stored in all the arbitrarily specified number of detailed log information elements 804, the failure occurrence pointer 801 up to the detailed log information element indicated by the registration pointer 803 in the direction indicated by the arrow 802 is stored. Move on. At this time, along with the movement of the failure occurrence pointer 801, the detailed log information 805 stored in the detailed log information element 804 is sequentially output, and the failure occurrence pointer 801 is deleted when the detailed log information element indicated by the registration pointer 803 is reached. To do.

Details of each of the above processes will be described with reference to the flowcharts of FIGS.
FIG. 9 is a diagram showing a basic processing flow performed by the computer system according to the present embodiment.
First, when the application program 110 is activated, the log output control program 120 is activated according to the activation instruction defined in the application program 110 (step 901).
The detailed log information storage unit 123 of the log output control program 120 generates a registration pointer indicating the detailed log information storage start position in the detailed log information holding area 129 (step 902).
The application program 110 reads and executes the defined instruction group sequentially from the top (step 903).
The error occurrence determination means 112 determines whether or not the instruction has been successfully executed (step 904), and if successful, reads the next instruction (step 905).
It is determined whether or not the read command is a detailed log output command (step 906). If the read command is a detailed log output command, the internal information transmission unit 111 executes a detailed log output process (step 907), and the next command Is read (step 908). In the detailed log output process, a detailed log output instruction read by specifying an argument as internal information of the application program 110 is executed, and the log output control program 120 generates detailed log information and stores it in the detailed log information storage area 129. Execute. Details will be described later with reference to the flowchart of FIG.
On the other hand, if it is not a detailed log output command, it is determined whether or not the end command of the application program 110 has been reached (step 909). If it has been reached, the processing is terminated. Repeat execution.
In step 904, when it is determined in step 903 that the instruction is not correctly executed and a program error has occurred, the control of the application program 110 is transferred to the catch clause (step 910). Here, the instruction execution failure corresponds to, for example, a case where a program error occurs when a character string other than a character string is specified in the argument 232 of the error generation instruction 220 shown in FIG.
Next, the program error information transmission unit 113 executes the failure log output process defined in the catch clause (step 911), and then reads the next instruction (step 908). In the fault log output process, the fault log output command defined in the catch clause is executed, and the process of generating fault log information and outputting it as a fault log message is executed. Details will be described later with reference to the flowchart of FIG.

FIG. 10 is a flowchart showing details of the process of the log output control program 120 corresponding to the detailed log output process of step 907.
First, the internal information receiving unit 121 receives an argument value as internal information transmitted by the internal information transmitting unit 111 of the application program 110 (step 1001).
It is determined whether or not a failure occurrence pointer exists in the detailed log information holding area 129 (step 1002), and if it does not exist, the internal information received by the internal information receiving unit 121 is transmitted to the detailed log information generating unit 122. Then, detailed log information is generated from the internal information (step 1003). In the generation of detailed log information, a message including the current time, the class name transmitted by the argument, and internal information is used as each data item.
Next, the detailed log information storage unit 123 stores the detailed log information generated by the detailed log information generation unit 122 in the detailed log information element pointed to by the registration pointer in the detailed log information holding area 129 (step 1004). Then, the registration pointer is moved to the next detailed log information element shown in FIG.
On the other hand, when the failure occurrence pointer exists in the detailed log information holding area 129 (step 1002), the detailed log information element counter value is incremented by “1” (step 1006). Here, the generation of the failure occurrence pointer will be described with reference to the flowchart of FIG.
The detailed log information element counter value is compared with a detailed log information element upper limit value (detailed log output number) arbitrarily specified in advance (step 1007), and the detailed log information element counter value is less than or equal to the detailed log information element upper limit value. If there is, detailed log information is generated and stored (steps 1003 to 1005).
On the other hand, when the detailed log information element counter value is larger than the upper limit value of the detailed log information element, the detailed log output means 126 outputs the detailed log information stored in the detailed log information element pointed to by the failure occurrence pointer, and the log message The detailed log information output by the generation unit 127 is read to generate a detailed log message, and the log message output unit 128 outputs it to the log recording device 130 (step 1008).
Next, the detailed log information stored in the detailed log information element pointed to by the failure occurrence pointer is deleted (step 1009), and the failure occurrence pointer is set at the position of the next detailed log information element (step 1010).
It is determined whether or not the failure occurrence pointer has reached the detailed log information element indicated by the registration pointer (step 1011). If the failure occurrence pointer has reached, the failure occurrence pointer is deleted (step 1012), and the failure log information element counter value is obtained. It is set to “0” (step 1013). Thereafter, detailed log information is generated and stored (steps 1003 to 1005).
On the other hand, when the failure occurrence pointer has not reached the detailed log information element indicated by the registration pointer, the output of detailed log information and the like are repeated (steps 1008 to 1010).

FIG. 11 is a flowchart showing details of the processing of the log output control program 120 corresponding to the failure log output processing in step 911.
First, the program error information receiving unit 124 receives the class name, message, and exception information as the program error information transmitted by the program error information transmitting unit 113 of the application program 110 (step 1101), and the detailed log output unit 126. (Step 1102).
The detailed log output request unit 126 generates an output pointer in the detailed log information holding area 129, and sets the position pointed to by the output pointer to the element at the position advanced by one from the detailed log information element pointed to by the registration pointer (step 1103). ).
Next, it is determined whether or not the detailed log information stored in the detailed log information element pointed to by the output pointer exists (step 1104). If the detailed log information does not exist, the position indicated by the output pointer is The process proceeds to the detailed log information element (step 1105), and it is determined whether or not the output pointer has reached the detailed log information element indicated by the registration pointer (step 1106). As a result of the determination, if the detailed log information element pointed to by the registration pointer has not been reached, it is determined whether or not the stored detailed log information exists (step 1104).
On the other hand, if detailed log information exists in the detailed log information element in step 1104, the detailed log information stored in the detailed log information element pointed to by the output pointer is output, and the log message generating unit 127 outputs the details. The log information is read, a detailed log message is generated and output to the log recording device 130 (step 1107).
Next, the detailed log information stored in the detailed log information element pointed to by the output pointer is deleted (step 1108), and the output pointer is set to the position of the next detailed log information element (step 1109).
It is determined whether or not the output pointer has reached the detailed log information element pointed to by the registration pointer (step 1110). If the output pointer has arrived, a failure occurrence pointer is generated and set at the position of the detailed log information element pointed to by the registration pointer. (Step 1111), the failure log information element counter value is set to “0” (Step 1112).
On the other hand, when the failure occurrence pointer has not reached the detailed log information element indicated by the registration pointer, the output of detailed log information and the like are repeated (steps 1107 to 1109).
Next, the failure log information generation unit 125 generates failure log information from the program error information received by the program error information reception unit 124 (step 1113). Here, the failure log information includes the current time and information on the method call stack of the exception acquired from the class name, message, and exception information transmitted as an argument of the failure log output command (called stack trace in Java). Generate.
The log message generation unit 127 reads the failure log information generated by the failure log information generation unit 125, generates a failure log message, outputs it to the log recording device 130, and ends the process (step 1114).

FIG. 12 is a diagram illustrating an example of a log file in which a detailed log message and a failure log message output to the log recording device as a result of the processing illustrated in FIGS. 9 to 11 are recorded.
Each log message recorded in the log file has data of time 1201, log type 1202, class name 1203, log message 1204.
The detailed log message 1205 is generated by concatenating the generation time 301 constituting the detailed log information shown in FIG. 3, the character string “DEBUG” indicating the log type, the class name 302, and the message 303 with “,”. To do. The detailed log message 1205 indicates that the detailed log information generated by the execution of the detailed log output command is output as the detailed log message, and the internal information of the application program 110 immediately before the execution of the error occurrence command is output. Is shown. The detailed log message group 1208 indicates that the detailed log information (number of detailed log information elements−1) pieces of detailed log information stored in the detailed log information holding area 129 immediately before the execution of the error occurrence instruction is output as the detailed log message. To express.
The failure log message 1206 is formed by concatenating the generation time 401 constituting the failure log information shown in FIG. 4, the character string “ERROR” indicating the log type, the class name 402, and the message 403 with “,”. It is generated by adding a new line and adding exception information 404. A failure log message 1206 represents a failure log message output by executing the failure log output command, and indicates that the execution of the error occurrence command has failed and control has been transferred to the catch clause. An exception message 1207 included in the failure log message 1206 corresponds to the exception information 404 included in the failure log information.
The detailed log message 1209 indicates that the detailed log information generated by the execution of the detailed log output command is output as the detailed log message, and indicates that the command after the occurrence of the failure is correctly executed. The detailed log message group 1210 after the occurrence of the failure includes (detail log information element upper limit value) pieces of detailed log information stored in the detailed log information holding area 129 after the output of the failure log message 1206, that is, after execution of the error occurrence instruction has failed. Indicates that it was output as a detailed log message.
The log message group 1211 indicates that a failure other than the failure indicated by the failure log message 1207 has occurred and a detailed log message and a failure log message have been output. In this case, after the failure occurs at the time “2005-02-23 17:49:43” indicated by the failure log message 1207, the failure occurs until the time “2005-02-23 18:59:02” indicated by the failure log message 1212. Indicates not.

With the above processing, in the log output control device according to the present embodiment, only a detailed log message within a certain range based on the time of the failure is recorded in the log storage device. Messages can be stored.
As the output form of the detailed log information stored in the detailed log information holding area in the log output control device of the present invention, a fixed number of detailed logs before and after the occurrence of the failure are output as shown in the above embodiment. For example, detailed log information for a certain period before and after the occurrence of a failure may be output.
Hereinafter, a mode of outputting detailed log information for a certain period before and after the occurrence of a failure will be described as a log output control device according to a second embodiment of the present invention.

FIG. 13 is an image diagram showing a detailed log information storage process in the detailed log information holding area 129 of the log output control apparatus according to the second embodiment.
In the present embodiment, the detailed log information holding area 129 is configured with a fixed-length data structure in which the leading end and the end of the array are connected and circular, and a buffer is used in units of seconds.
In FIG. 13, each detailed log information element 1301 can store one piece of time information. This time information is referred to as detailed log information time.
The detailed log information list 1302 is a variable-length array that can store a plurality of detailed log information, and has a data structure that allows the detailed log information to be read from the top of the list and the detailed log information to be added to the end of the list Represents. A line segment 1303 indicates that the detailed log information element 1301 holds one detailed log information list 1302.
The registration pointer 1304 points to the detailed log information element that is the current detailed log information storage position, and the registration pointers 1305 to 1307 point to the detailed log information element that is the past detailed log information storage position. An arrow 1308 indicates the moving direction of the registration pointer.
Detailed log information 1309 indicates information stored in the detailed log information element, and detailed log information 1310 indicates information newly stored in the detailed log information element.
In the present embodiment, the registration pointer 1304 is first located at the position of the registration pointer 1305 when the log output control program 120 is activated. Next, the registration pointer 1304 indicates the direction indicated by the arrow 1308 as indicated by the registration pointers 1305 to 1307 every time the detailed log information time is added by one second by the detailed log information storage unit 123 (every second has elapsed). Next, the detailed log information elements are moved in order.
The detailed log information 1310 is stored at the end of the detailed log information list held by the detailed log information element indicated by the registration pointer 1304.

Based on the above configuration, each process performed by the log output control apparatus according to the second embodiment of the present invention will be described using a flowchart.
The basic processing performed by the computer system according to the present embodiment is substantially the same as the processing shown in the flowchart of FIG. 9, but in addition to the processing in step 902, the current time is acquired and the acquired current time is used as the detailed log information. As the time, a process of storing in the detailed log information element at the position indicated by the registration pointer is performed. Note that the minimum unit of time handled in this embodiment is seconds.

FIG. 14 is a flowchart showing details of the processing of the log output control program 120 corresponding to the detailed log output processing in step 907 of FIG.
First, the internal information receiving unit 121 receives an argument value as internal information transmitted by the internal information transmitting unit 111 of the application program 110 (step 1401), and acquires the current time (step 1402).
The acquired current time is compared with the detailed log information time of the detailed log information element pointed to by the registration pointer, and it is determined whether or not the two times coincide (step 1403).
If both times match as a result of the determination, the internal information received by the internal information receiving means 121 is transmitted to the detailed log information generating means 122, and detailed log information is generated from the internal information (step 1404).
Next, the detailed log information storage unit 123 stores the detailed log information generated by the detailed log information generation unit 122 at the end of the detailed log information list of the detailed log information element indicated by the registration pointer in the detailed log information holding area 129. Then, the process ends (step 1405).
On the other hand, if the two times do not match in step 1403, the detailed log information time of the detailed log information element pointed to by the registration pointer is acquired and added to the time by 1 second to generate the next detailed log information time ( Step 1406).
Next, the registration pointer is set in the next detailed log information element (step 1407), the next detailed log information time generated in step 1406 is set in the detailed log information element (step 1408), and the detailed log information list Is emptied (step 1409).
Next, it is determined whether or not a failure occurrence pointer exists in the detailed log information holding area 129 (step 1410). If a failure occurrence pointer exists, the detailed log information element counter value is increased by “1” ( Step 1411).
The detailed log information element counter value is compared with the detailed log information element upper limit value arbitrarily specified in advance (step 1412), and when the detailed log information element counter value is larger than the detailed log information element upper limit value, it will be described later. Detailed log message output processing is performed (step 1413).
On the other hand, if it is determined in step 1410 that a failure occurrence pointer exists, if it is determined in step 1412 that the detailed log information element counter value is equal to or less than the detailed log information element upper limit value, or a detailed log message output process is performed in step 1413 Thereafter, the current time is compared with the detailed log information time of the detailed log information element pointed to by the registration pointer, and it is determined whether or not the two times match (step 1414). Are generated and stored (1404, 1405). On the other hand, if they do not match, the processing from step 1406 is repeated.

FIG. 15 is a flowchart showing details of the detailed log message output process shown in step 1413.
In this process, first, it is determined whether or not the detailed log information list of the detailed log information element pointed to by the failure occurrence pointer is not empty (step 1501). If it is not empty, the details stored in the detailed log information list are determined. The log information is output, the detailed log information output by the log message generating means 127 is read, a detailed log message is generated and output to the log recording device (step 1502).
Next, the detailed log information list of the detailed log information element indicated by the failure occurrence pointer is emptied (step 1503), and the failure occurrence pointer is set at the position of the next detailed log information element (step 1504).
It is determined whether or not the failure occurrence pointer has reached the detailed log information element indicated by the registration pointer (step 1505). If the failure occurrence pointer has reached, the failure occurrence pointer is deleted (step 1506), and the detailed log information element counter value is obtained. The initial value is set to “1” and the process is terminated (step 1507).
On the other hand, if not reached in step 1505, the process returns to step 1501 to repeat the process.

FIG. 16 is a flowchart showing details of the processing of the log output control program 120 corresponding to the failure log output processing in step 911 of FIG.
First, the program error information receiving unit 124 receives the class name, the message, and the argument value as exception information as the program error information transmitted by the program error information transmitting unit 113 of the application program 110 (step 1601). The detailed log output means 126 is notified (step 1602).
The detailed log output request unit 126 generates an output pointer in the detailed log information holding area 129, and sets the position pointed to by the output pointer to the element at the position advanced by one from the detailed log information element pointed to by the registration pointer (step 1603). ).
Next, it is determined whether or not the detailed log information stored in the detailed log information list of the detailed log information element indicated by the output pointer exists (step 1604). If the detailed log information does not exist, the output pointer is The position pointed to is advanced to the next detailed log information element (step 1605), and it is determined whether or not the output pointer has reached the detailed log information element pointed to by the registration pointer (step 1606). As a result of the determination, if the detailed log information element pointed to by the registration pointer has not been reached, it is determined whether or not the stored detailed log information exists (step 1604).
On the other hand, if there is detailed log information stored in the detailed log information list of the detailed log information element in step 1604, the detailed log information stored in the detailed log information list of the detailed log information element pointed to by the output pointer is displayed. The detailed log information output is read by the log message generation unit 127, and a detailed log message is generated and output to the log recording device 130 (step 1607).
Next, the detailed log information stored in the detailed log information list of the detailed log information element pointed to by the output pointer is deleted (step 1608), and the output pointer is set to the position of the next detailed log information element (step 1609).
It is determined whether or not the output pointer has reached the detailed log information element pointed to by the registration pointer (step 1610). If the output pointer has reached, a failure occurrence pointer is generated and set to the position of the detailed log information element pointed to by the registration pointer. (Step 1611), the failure log information element counter value is set to “1” (Step 1612).
Next, the failure log information generation unit 125 generates failure log information from the program error information received by the program error information reception unit 124 (step 1613).
The log message generation unit 127 reads the failure log information generated by the failure log information generation unit 125, generates a failure log message, outputs it to the log recording device 130, and ends the process (step 1614).
On the other hand, when the output pointer has not reached the detailed log information element indicated by the registration pointer, the output of the detailed log information is repeated (steps 1607 to 1609).

As a result of the above processing, the log output control apparatus according to the present embodiment also logs only the detailed log messages in a certain range based on the time of the failure, as in the log output control apparatus according to the first embodiment. Since it is recorded in the storage device, the log message can be efficiently stored in the log storage device.
Note that the number of elements in the detailed log information holding area and the upper limit value of the detailed log information element of the log output control apparatus according to this embodiment are appropriately determined in consideration of the performance of the computer system to which the present invention is applied. desirable.

It is a block diagram which shows schematic structure of the computer system which comprises the log output control apparatus which concerns on one embodiment of this invention. It is a figure which shows an example of the source code of the application program which comprises a computer system. It is a figure which shows an example of the data structure of detailed log information. It is a figure which shows an example of the data structure of failure log information. It is an image figure which shows the storage process of the detailed log information to the detailed log information holding area | region which concerns on 1st Embodiment of this invention. It is an image figure which shows the output process of the detailed log information from the detailed log information holding area | region which concerns on 1st Embodiment of this invention at the time of failure occurrence. It is an image figure which shows the storage process of the detailed log information to the detailed log information holding area | region which concerns on 1st Embodiment of this invention after failure generate | occur | produces. It is an image figure which shows the output process of the detailed log information from the detailed log information holding area | region which concerns on 1st Embodiment of this invention after failure generate | occur | produces. It is a flowchart which shows the basic processing which the computer system which concerns on 1st Embodiment of this invention performs. It is a flowchart which shows the detail of a process of the log output control program corresponding to a detailed log output process. It is a flowchart which shows the detail of a process of the log output control program corresponding to a failure log output process. It is a figure which shows an example of the data structure of the log file recorded on a log storage device. It is an image figure which shows the storage process of the detailed log information to the detailed log information holding area | region which concerns on 2nd Embodiment of this invention. It is a flowchart which shows the detail of a process of the log output control program corresponding to the detailed log output process which concerns on 2nd Embodiment of this invention. It is a flowchart which shows the detail of a detailed log message output process. It is a flowchart which shows the detail of a process of the log output control program corresponding to the failure log output process which concerns on 2nd Embodiment of this invention.

Explanation of symbols

  110 Application program, 111 Internal information transmission means, 112 Error information determination means, 113 Program error information transmission means, 120 Log output control program, 121 Internal information reception means, 122 Detailed log information generation means, 123 Detailed log information storage means, 124 Program error information receiving means, 125 fault log information generating means, 126 detailed log output requesting means, 127 log message generating means, 128 log message output means, 129 detailed log information holding area, 130 log storage device.

Claims (6)

In a log output control device that generates a log message based on internal information output from an application program and program error information and stores it in a storage device,
Means for storing the internal information in a temporary storage area;
Means for acquiring internal information in an arbitrary range based on the reception time of the program error information from the temporary storage area, and generating the log message;
A log output control device comprising: means for storing the generated log message in the storage device. The internal information of the arbitrary range is
2. The log output control apparatus according to claim 1, wherein a predetermined number of internal information before and after the internal information stored when the program error information is received is used as a reference. The internal information of the arbitrary range is
2. The log output control device according to claim 1, wherein the log output control device indicates internal information stored within a predetermined time before and after the time when the program error information is received. In a log output control program for causing a computer to execute a process of generating a log message and storing it in a storage device based on internal information output from an application program and program error information,
Processing for storing the internal information in a temporary storage area;
Processing for acquiring internal information stored in an arbitrary range based on the reception time of the program error information from the temporary storage area and generating the log message;
A log output control program that causes the computer to execute a process of storing a generated log message in the storage device. The internal information of the arbitrary range is
5. The log output control program according to claim 4, wherein the log output control program indicates a predetermined number of internal information before and after the internal information stored when the program error information is received. The internal information of the arbitrary range is
5. The log output control program according to claim 4, wherein the log output control program indicates internal information stored within a predetermined time before and after the time when the program error information is received.

Images