JP2009277119A - Log recording system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To record a plurality of pieces of log information concerning transaction in a recording order matching an actual processing order in a system for executing transaction while a plurality of servers are in cooperation with one another. <P>SOLUTION: Log collection servers 102-1 to 102-3 send a transaction ID and an order information showing a processing order in the log collection servers 102-1 to 102-3 together with a log message, to a log control server 101. The log control server 101 records a plurality of log messages received from the log collection servers 102-1 to 102-3 in a processing order in the log collection servers 102-1 to 102-3 based on the transaction ID and the order information added to the received log message. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a log recording system for recording log information of a plurality of servers.

  FIG. 17 shows a configuration example of a conventional log recording system. In this log recording system, the client terminal 11 transmits a processing request to the server 12, the server 12 transfers the processing request to the server 13, and the server 13 executes the requested processing. Then, the processing result from the server 13 is returned to the client terminal 11 via the server 12. A series of processing from transmission of a processing request by the client terminal 11 to reception of a processing result is defined as one transaction.

  At this time, the servers 12 and 13 execute one transaction in cooperation with each other, but log information of processing in each server is recorded in the log files 14 and 15 for each server.

There is also known a system that includes a plurality of servers that acquire log information and a collection and accumulation control device that collects and accumulates the log information, and the collection and accumulation control device accumulates log information received from each server in time series (for example, , See Patent Document 1 below).
JP 2001-027990 A

The conventional log recording system described above has the following problems.
In a system in which a plurality of servers cooperate with each other to execute a transaction, the system clock of each server is rarely synchronized. If there is a difference in the system clock of each server and the log information is recorded for each server, the recording order of the log information of each server related to one transaction may not match the actual processing order. .

  For example, the time at which the server 12 in FIG. 17 receives the processing request is recorded in the log file 14 at 12:20, and the time at which the server 13 transmits the processing result is recorded in the log file 15 at 12:18. Can be considered. In this case, a log file is generated as if the processing of the server 12 is executed after the processing of the server 13.

  When a failure occurs in such a system, it is very important to understand the context of each process by referring to the log file in the failure investigation. However, in an environment where log information is recorded for each server, there is a problem that it is difficult to grasp the context of processing, and it takes time to find a fault location.

  An object of the present invention is to record a plurality of log information related to a transaction in a recording order that matches the actual processing order in a system in which a plurality of servers execute transactions in cooperation with each other.

  The disclosed log recording system includes a plurality of log collection servers that execute transactions in cooperation and collect log information related to the transactions, and a log management server that records log information.

  Each log collection server includes an adding unit and a transmitting unit. The adding means adds the transaction identification information of the transaction and the order information indicating the processing order between the plurality of log collection servers to the collected log information. The transmission unit transmits the log information to which the transaction identification information and the order information are added to the log management server.

  The log management server includes a receiving unit and a recording unit. The receiving means receives log information from a plurality of log collection servers. The recording means records the plurality of log information received from the plurality of log collection servers in the processing order between the log collection servers based on the transaction identification information and the order information added to the received log information.

  By adding sequence information indicating the processing order between multiple log collection servers that execute a single transaction in conjunction with each log information and sending it to the log management server, logs are processed according to the processing order between those log collection servers. You can sort the information. Therefore, the transaction processing order in the log file is guaranteed.

  In a system in which a plurality of servers cooperate with each other to execute a transaction, a plurality of log information related to the transaction is recorded in a recording order that matches the actual processing order.

The best mode for carrying out the present invention will be described below in detail with reference to the drawings.
The log recording system of the embodiment aggregates log information generated for each server into a single log management server, and generates a log file that guarantees the transaction processing order. More specifically, the following processing is performed.
(1) Generation of identification information (transaction ID) that uniquely identifies a transaction, triggered by the start of the transaction.
(2) Generate order information (log output classification) indicating the processing order between servers that execute one transaction in cooperation.
(3) A transaction ID, a log output category, and a sequence number that guarantees the log output order are added to the log information output by each server.
(4) The log information is rearranged according to the information added to the log information and output to a log file.

  FIG. 1 shows a configuration example of a log recording system according to the embodiment. This log recording system includes a log management server 101 and log collection servers 102-1 to 102-3. The log management server 101 includes a sequence reception unit 111, a retransmission request unit 112, a log monitoring unit 113, a sequence management unit 114, a sequence map 115, and a log file 116. Each log collection server 102-i (i = 1, 2, 3) includes a log message transmission unit 121-i, a log message retransmission unit 122-i, and a transmission message list 123-i.

  The log message transmission unit 121-i transmits a log message generated in the processing of the log collection server 102-i to the log management server 101, and registers the transmitted log message in the transmission message list 123-i. The sequence receiving unit 111 receives the log message, transfers it to the log monitoring unit 113, and registers the log message in the sequence map 115.

  The resending request unit 112 refers to the sequence map 115 and transmits resending requests for unreachable log messages to the log collection servers 102-1 to 102-3. The log message retransmission unit 122-i of the log collection server 102-i that has received the retransmission request acquires the requested log message from the transmission message list 123-i and retransmits it to the log management server 101.

  The sequence management unit 114 refers to the sequence map 115 and outputs log messages from the log collection servers 102-1 to 102-3 to the log file 116 in the order of occurrence. The log monitoring unit 113 monitors log messages from the log collection servers 102-1 to 102-3, and determines whether or not each log collection server is normal.

The log collection servers 102-1 to 102-3 are classified into, for example, a Web server and an application (AP) server.
As shown in FIG. 2, the Web server 202 receives a processing request from the client terminal 201 and transfers it to the AP server 203. The AP server 203 is an application for various business operations such as personnel management, finance, and insurance. Execute the program and perform spreadsheet processing. Then, the processing result from the AP server 203 is returned to the client terminal 201 via the Web server 202. Thus, the Web server 202 and the AP server 203 execute one transaction in cooperation with each other.

Next, the operation of the log recording system of FIG. 1 will be described in more detail with reference to FIGS.
FIG. 3 is a flowchart of the log message transmission process. The log message transmission unit 121-i adds a transaction ID, a log output category, and a sequence number for each log output category to the generated log message (step 301).

  For example, a business ID is used as the transaction ID. The log output category is a category of log messages output from the log collection servers 102-1 to 102-3, and is changed each time the server that executes processing in one transaction is switched.

  In the example of FIG. 2, the log output classification is first given when a processing request is transmitted from the client terminal 201 to the Web server 202. Thereafter, the log output classification “1” is added to the log message transmitted by the Web server 202.

  Next, the log output classification is given when the processing in the Web server 202 is finished and a processing request is transmitted from the Web server 202 to the AP server 203. Thereafter, the log output classification “2” is added to the log message transmitted by the AP server 203.

  The log output category is added last when the processing in the AP server 203 is finished and the processing result is transmitted from the AP server 203 to the Web server 202. Thereafter, the log output classification “3” is added to the log message transmitted by the Web server 202.

  By adding such log output classification to the log message, it is possible to determine the processing order among the log collection servers 102-1 to 102-3. Furthermore, by adding a series of sequence numbers to a plurality of log messages belonging to each log output category, it becomes possible to determine the processing order in each log collection server 102-i.

FIG. 4 shows an example of the transaction ID, log output classification, and sequence number added to each log message.
In this example, the Web server 202 outputs six log messages in the “business A” transaction. Among them, the log output classification “1” is added to the three log messages, and the sequence numbers “1”, “2”, and “3” are added in order. The remaining three log messages are added with a log output category “3”, and sequence numbers “1”, “2”, and “3” are added in order. On the other hand, the log output classification “2” is added to the three log messages of the AP server 203, and the sequence numbers “1” and “2” are added.
, “3” are added in order.

  Next, the log message transmission unit 121-i transmits the log message to the log management server 101, and registers the transmitted log message in the transmission message list 123-i (step 302).

  FIG. 5 shows an example of a transmission message list of the AP server 203. Each log message of the AP server 203 is registered in this transmission message list together with the transaction ID, log output classification, and sequence number shown in FIG.

  FIG. 6 is a flowchart of the sequence reception process. The sequence receiving unit 111 receives the log message transmitted from each log collection server 102-i, and writes the log message in the sequence map 115 together with the transaction ID, log output classification, and sequence number (step 601).

  At this time, as shown in FIG. 7, log messages having the same transaction ID and log output classification are written in the sequence map 115 in ascending order of sequence numbers, and “SKIP” is written in the log state. However, “WRITE” is written in the log state of the log message having the log output category “1” and the sequence number “1”. “WRITE” indicates a state that can be output to the log file 116, and “SKIP” indicates a state that cannot be output to the log file 116.

  On the other hand, when a log message whose sequence number is not in ascending order is received, an entry having an unreachable sequence number is added before the entry of the log message, and “NULL” indicating an unreachable state is added to the log state. Write. Then, the retransmission request unit 112 is requested to perform a retransmission request process.

  In the example of FIG. 7, the log message having the log output category “2” and the sequence number “3” is received in the state where the log message having the log output category “2” and the sequence number “2” is not received. Yes. In this case, since the sequence numbers are not in ascending order, an entry having a log output category “2”, a sequence number “2”, and a log state “NULL” is added.

  Next, the sequence receiving unit 111 changes the log state of the sequence map 115 (step 602). At this time, the log status of the entry having the same transaction ID and log output classification as the target entry having the log status “SKIP” and having a sequence number smaller by 1 than the sequence number of the target entry is referred to. If the log status of the entry is “WRITE”, the log status of the target entry is changed from “SKIP” to “WRITE”.

  In the case of the entry having the log output category “1” and the sequence number “2” in FIG. 7, the log status of the immediately preceding entry is “WRITE”, so that the log status is changed from “SKIP” as shown in FIG. Changed to “WRITE”.

  Further, if the log message of the target entry is the final message (log end message) in the log output category, the log status of the entry having the sequence number “1” in the next log output category is changed from “SKIP” to “WRITE”. change. Thus, unless there is an unreached log message, the log status is changed to “WRITE” in ascending order of the log output category and sequence number.

  FIG. 9 is a flowchart of the sequence management process. The sequence management unit 114 refers to the sequence map 115 and writes log messages having the same transaction ID and log output classification and having the log state “WRITE” to the log file 116 in ascending sequence number order (step 901). At this time, the log message having the log state “SKIP” is skipped.

  Next, it is checked whether or not the last written log message is a log end message (step 902). If it is a log end message, the processing of step 901 is repeated for the next log output category. If the last written log message is not a log end message, the process ends.

  FIG. 10 shows an example of the log file 116 generated in this way. In this example, the transaction ID, the name of the server that performed the process, the client ID of the client terminal 201, and the log message are written in the log file 116.

  According to such sequence management processing, the received log messages are written to the log file 116 in the ascending order of the log output category and in the ascending order of the sequence numbers. Therefore, even if there is a difference in processing speed or system clock between the log collection servers 102-1 to 102-3, log messages can be recorded in the log file 116 in a recording order that matches the transaction processing order.

  In this way, the log information of the log collection servers 102-1 to 102-3 is aggregated in one log management server 101, and the log file 116 that guarantees the transaction processing order is generated. As a result, it is not necessary to collect log information of each server when a failure occurs or to take into account differences in system clocks, and the burden of log analysis work is greatly reduced.

  FIG. 11 is a flowchart of the retransmission request process. When the retransmission request unit 112 is requested to perform retransmission request processing from the sequence receiving unit 111 or the log monitoring unit 113, the retransmission request unit 112 searches for an entry having a log state “NULL” in the sequence map 115. Then, a log message retransmission request is transmitted to the log collection server 102-i corresponding to the log output category of the entry (step 1101).

For example, in the example of FIG. 7, since the log output category of the entry having the log state “NULL” is “2”, a retransmission request is transmitted to the corresponding AP server.
When the requested log message is received from the log collection server 102-i, the log status is changed from “NULL” to “SKIP” as shown in FIG. 12 (step 1102).

  FIG. 13 is a flowchart of log message retransmission processing. The log message retransmission unit 122-i of the log collection server 102-i that has received the log message retransmission request retrieves the requested log message from the transmission message list 123-i (step 1301). The log message is retransmitted to the log management server 101 (step 1302).

  According to such retransmission request processing and log message retransmission processing, even when the log message is lost for some reason before transmission or after transmission, the log management server 101 can reliably acquire the log message.

FIG. 14 is a flowchart of the log monitoring process. The log collection servers 102-1 to 102-3 start sending survival confirmation messages at regular intervals, triggered by sending the first log message (processing start message) to the log management server 101. This survival confirmation message is also transmitted to the log management server 101 as a log message.

  The log monitoring unit 113 monitors the log collection server 102-i with a monitoring timer when receiving a processing start message from the log collection server 102-i (step 1401). Then, it is checked whether or not a survival confirmation message has been received within a certain time (step 1402). If a survival confirmation message is received within a certain time, the monitoring timer is reset (step 1403), and monitoring of the log collection server 102-i is continued.

  Next, it is checked whether or not a log end message has been received (step 1404). If no log end message has been received, the processing from step 1402 is repeated. When the log end message is received, monitoring of the log collection server 102-i is terminated.

  On the other hand, if the existence confirmation message is not received within a predetermined time in step 1402, it is determined that the transaction is abnormal, and a retransmission request process is requested to the retransmission request unit 112 (step 1405).

  By monitoring the survival confirmation message that is always transmitted, it is possible to immediately detect the abnormality of the log collection server 102-i and perform the retransmission request process without waiting for the reception of the next log message.

Although the log recording system of FIG. 1 includes three log collection servers, in general, the number of log collection servers in the log recording system may be two or more.
The log management server 101 and the log collection servers 102-1 to 102-3 in FIG. 1 are configured using, for example, an information processing apparatus (computer) as shown in FIG. 15 includes a CPU 1501, a memory 1502, an input device 1503, an output device 1504, an external storage device 1505, a medium drive device 1506, and a network connection device 1507, which are connected to each other via a bus 1508.

  The memory 1502 includes, for example, a read only memory (ROM), a random access memory (RAM), and the like, and stores programs and data used for processing. The data stored in the memory 1502 includes the sequence map 115 or the transmission message lists 123-1 to 123-3. The CPU 1501 performs processing of the log management server 101 or the log collection servers 102-1 to 102-3 by executing a program using the memory 1502.

  The input device 1503 is, for example, a keyboard, a pointing device, and the like, and is used for inputting instructions and information from an operator. The output device 1504 is, for example, a display, a printer, a speaker, and the like, and is used to output an inquiry to the operator and a processing result.

  The external storage device 1505 is, for example, a magnetic disk device, an optical disk device, a magneto-optical disk device, a tape device, or the like. The information processing apparatus stores programs and data in the external storage device 1505, and loads them into the memory 1502 for use as necessary. The data stored in the external storage device 1505 includes a log file 116.

The medium driving device 1506 drives a portable recording medium 1509 and accesses the recorded contents. The portable recording medium 1509 is an arbitrary computer-readable recording medium such as a memory card, a flexible disk, an optical disk, or a magneto-optical disk. The operator stores programs and data in the portable recording medium 1509, and loads them into the memory 1502 for use as necessary.

  A network connection device 1507 is connected to a communication network such as a local area network (LAN) and performs data conversion accompanying communication. Also, the information processing apparatus receives programs and data from an external apparatus via the network connection apparatus 1507 as necessary, and loads them into the memory 1502 for use.

  FIG. 16 shows a method for providing a program and data to the information processing apparatus of FIG. Programs and data stored in the portable recording medium 1509 and the database 1611 of the external device 1601 are loaded into the memory 1502 of the information processing device 1602. The external device 1601 generates a carrier signal that carries the program and data, and transmits the carrier signal to the information processing device 1602 via any transmission medium on the communication network. The CPU 1501 executes the program using the data and performs the above-described processing.

It is a block diagram of the log recording system of an embodiment. It is a figure which shows a Web server and AP server. It is a flowchart of a log message transmission process. It is a figure which shows transaction ID, a log output division, and a sequence number. It is a figure which shows a transmission message list. It is a flowchart of a sequence reception process. It is a figure which shows a 1st sequence map. It is a figure which shows a 2nd sequence map. It is a flowchart of a sequence management process. It is a figure which shows a log file. It is a flowchart of a resending request process. It is a figure which shows a 3rd sequence map. It is a flowchart of a log message resending process. It is a flowchart of a log monitoring process. It is a block diagram of information processing apparatus. It is a figure which shows the provision method of a program and data. It is a block diagram of the conventional log recording system.

Explanation of symbols

DESCRIPTION OF SYMBOLS 11, 201 Client terminal 12, 13 Server 14, 15, 116 Log file 101 Log management server 102-1, 102-2, 102-3 Log collection server 111 Sequence receiving part 112 Retransmission request part 113 Log monitoring part 114 Sequence management part 115 Sequence Map 121-1, 121-2, 121-3 Log Message Transmission Unit 122-1, 122-2, 122-3 Log Message Retransmission Unit 123-1, 123-2, 123-3 Transmission Message List 202 Web Server 203 AP server 1501 CPU
1502 Memory 1503 Input device 1504 Output device 1505 External storage device 1506 Medium drive device 1507 Network connection device 1508 Bus 1601 External device 1602 Information processing device 1611 Database

Claims (3)

A log recording system having a plurality of log collection servers that execute transactions in cooperation and collect log information related to the transactions, and a log management server that records the log information,
Each log collection server
Adding means for adding transaction identification information of the transaction and order information indicating a processing order between the plurality of log collection servers to the collected log information;
Transmission means for transmitting the log information to which the transaction identification information and order information are added to the log management server,
The log management server
Receiving means for receiving the log information from the plurality of log collection servers;
Recording means for recording a plurality of log information received from the plurality of log collection servers in a processing order between the plurality of log collection servers based on the transaction identification information and the order information added to the received log information; A log recording system comprising:   The adding means of each log collection server further adds a sequence number indicating a recording order of a plurality of log information collected by the log collection server in the transaction, and the recording means includes a plurality of the same order information added. The log recording system according to claim 1, wherein the log information is recorded in the order of the sequence numbers added to the plurality of log information.   The log management server includes a first storage unit that stores an entry including received log information, transaction identification information added to the received log information, order information, sequence number, and log status information; A second storage means for storing a log file, wherein the recording means outputs a plurality of log information having the same transaction identification information and order information in ascending order of sequence numbers together with log status information indicating that output is impossible; When the last log information having the same transaction identification information and sequence information is received, the next sequence information is stored. Change the log status information of each entry from not outputable to outputable, and then add the same transaction identification information and order It includes information and logging system of claim 2, wherein the log information of a plurality of entries, and writes to the log file in ascending order of the sequence number having a log status information indicating possible output.

Images