JP6957396B2 - Management device, server device, log management method, management program and server program - Google Patents

Description

The present invention relates to a management device, a server device, a log management method, a management program, and a server program.

Patent Document 1 discloses a technique in which each of a plurality of servers operating in cooperation with each other creates a log.

Japanese Unexamined Patent Publication No. 2011-100228

When determining the operating status of a system in which multiple servers are linked, it is necessary to understand the processing results of events executed on each server by associating the corresponding ones such as "send" and "receive". It is difficult for such reasons.

Since each server operates in multitasking, logs of various events are recorded in a mixed manner, and the OS time of each server does not match in milliseconds even if NTP etc. is used, so the order of the events recorded in the log. And it is difficult to grasp the association from the date and time of occurrence. "OS" is an abbreviation for Operating System. "NTP" is an abbreviation for Network Time Protocol.

In particular, in the servers that make up recent systems, various software such as IIS, Tomcat, and Oracle (registered trademark) are available on various OSs such as Windows (registered trademark) and Linux (registered trademark) due to the trend of openness. in use. "IIS" is an abbreviation for Internet Information Services. Each server is managed in a closed world, and there is no function to grasp the relationship with other servers. At present, the only information that is commonly used by all servers and can be used to understand the relationship between operations is the system time.

In such a situation, it is difficult to grasp the flow of a series of operations between the servers, so that it is difficult to grasp the problematic part when a failure occurs. It is difficult to set the system time, which helps when associating operations between servers, in milliseconds even using NTP, etc., and some servers output a large number of logs per second, so the association is clear. It is insufficient as information for judgment.

An object of the present invention is to clearly associate a series of processes executed in cooperation between servers.

The management device according to one aspect of the present invention is
A receiver that receives request data that notifies the type of processing executed by each server device as an event from multiple server devices that execute individual processes in cooperation with each other.
When the data for notifying the first event of a series of events classified into the same group in the setting information stored in the memory and the order in the corresponding group is defined is received by the receiving unit as the request data. A first transmission unit that assigns an identifier to the server and transmits the first response data including the assigned identifier to the server device that is the source of the request data.
When the data notifying the second and subsequent events in the series of events is received by the receiving unit as the request data, the second response instructing to use the identifier given by the first transmitting unit. It includes a second transmission unit that transmits data to the server device that transmits the request data.

The first transmission unit includes the assigned identifier, and instructs other server devices that execute the next process of the process executed by the server device that transmits the request data to notify the assigned identifier. The data is transmitted as the first response data,
The second response data is data instructing the second transmission unit to use an identifier notified from another server device that executes a process before the process executed by the server device that is the source of the request data. Send as.

When the data for notifying the second and subsequent events other than the last of the series of events is received by the receiving unit as the request data, the second transmitting unit is the server device of the source of the request data. Instructs to use the identifier notified from the other server device that executes the process before the process executed in, and the notified identifier is the process executed by the server device that sends the request data. The data instructing the other server device that executes the next process to be notified is transmitted as the second response data.

The first transmission unit includes information on the date and time when the identifier is given in the identifier to be given.

The first transmission unit includes the count number stored in the memory in the identifier to be assigned, and then increments the count number stored in the memory.

When the date changes, the first transmission unit resets the count number stored in the memory to an initial value.

The first transmission unit includes the count number stored in the memory and the reset number stored in the memory in the identifier to be assigned, and when the count number stored in the memory reaches the maximum value, the memory Instead of incrementing the count number stored in, the initial value is reset, and the reset number stored in the memory is incremented.

When the date changes, the first transmission unit resets the reset number stored in the memory to the initial value.

A server device that executes processing in cooperation with another server device according to one aspect of the present invention is
A transmission unit that transmits request data for notifying the type of processing as an event to a management device to which an identifier is assigned.
When the data for notifying the first event of a series of events classified into the same group and the order in the corresponding group is defined is transmitted as the request data by the transmission unit, the management device can display the data. A first receiving unit that receives the first response data including the identifier given by the management device, and
When the data notifying the second and subsequent events in the series of events is transmitted by the transmission unit as the request data, the management device instructs the management device to use the identifier given by the management device. A second receiving unit that receives the second response data and also receives the call data notifying the identifier assigned by the management device from another server device that executes the process before the process.
When the first response data is received by the first receiving unit, the process is executed and a log recording an identifier included in the first response data is output, and the second response data is the second response data. (2) When received by the receiving unit, it includes an executing unit that executes the processing and outputs a log recording the identifier notified by the calling data.

The first receiving unit includes the identifier given by the management device, and sends data instructing the other server device that executes the next process of the process to notify the assigned identifier to the first response. Received as data
When the first response data is received by the first receiving unit, the transmitting unit executes the call data notifying the identifier included in the first response data to the next processing of the processing. Send to the server device.

When the second response data is received by the second receiving unit, the transmitting unit generates another calling data notifying the identifier notified by the calling data if there is a next processing of the processing. Then, the generated call data is transmitted to another server device that executes the next process of the process.

In the log management method according to one aspect of the present invention,
Multiple server devices that execute individual processes in cooperation with each other send request data that notifies the type of process executed by each server device as an event to the management device that assigns an identifier.
When the management device receives data notifying the first event of a series of events classified into the same group and whose order is defined in the group as the request data, an identifier is assigned. The first response data including the assigned identifier is transmitted to the server device that is the source of the request data, and the data is transmitted.
When each server device receives the first response data, the processing of each server device is executed, and a log recording the identifier included in the first response data is output.
When the management device receives data notifying the second and subsequent events in the series of events as the request data, the second response data instructing the management device to use the identifier assigned by the management device is provided. It is transmitted to the server device that is the source of the request data, and
When each server device receives the second response data, it receives call data notifying the identifier assigned by the management device from another server device that executes the processing before the processing of each server device. , The processing of each server device is executed, and the log recording the identifier notified by the call data is output.

The management program according to one aspect of the present invention is
On the computer
A reception procedure for receiving request data that notifies the type of processing executed by each server device as an event from multiple server devices that execute individual processes in cooperation with each other.
When the data notifying the first event of a series of events classified into the same group in the setting information stored in the memory and the order in the corresponding group is defined is received as the request data by the reception procedure. The first transmission procedure of assigning an identifier to the server and transmitting the first response data including the assigned identifier to the server device that is the source of the request data.
When the data notifying the second and subsequent events in the series of events is received as the request data by the receiving procedure, the second response instructing to use the identifier given by the first transmitting procedure. The second transmission procedure of transmitting the data to the server device that transmits the request data is executed.

The server program according to one aspect of the present invention
To a computer that is a server device that executes processing in cooperation with other server devices
A transmission procedure for transmitting request data for notifying the type of processing as an event to a management device to which an identifier is assigned, and
When the data notifying the first event of a series of events classified into the same group and the order in the corresponding group is defined is transmitted as the request data by the transmission procedure, the management device can display the data. The first receiving procedure for receiving the first response data including the identifier given by the management device, and
When the data notifying the second and subsequent events in the series of events is transmitted as the request data by the transmission procedure, the management device instructs the management device to use the identifier given by the management device. A second reception procedure for receiving the second response data and receiving call data notifying the identifier assigned by the management device from another server device that executes the process before the process.
When the first response data is received by the first reception procedure, the process is executed and a log recording the identifier included in the first response data is output, and the second response data is the first response data. (2) When the data is received by the receiving procedure, the processing is executed and the execution procedure of outputting the log recording the identifier notified by the calling data is executed.

In the present invention, a series of processes executed in cooperation between servers are grouped by an identifier. Therefore, according to the present invention, these series of processes can be clearly related.

The block diagram which shows the structure of the log management system which concerns on Embodiment 1. FIG. The block diagram which shows the structure of the management apparatus which concerns on Embodiment 1. FIG. The block diagram which shows the structure of the server apparatus which concerns on Embodiment 1. FIG. The flowchart which shows the operation of the management apparatus which concerns on Embodiment 1. An explanatory table of each numerical value of the group ID according to the first embodiment. The block diagram which shows the structure of the log management system which concerns on application example of Embodiment 1. FIG. 3 is a processing transition diagram of a log management system according to an application example of the first embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each figure, the same or corresponding parts are designated by the same reference numerals. In the description of the embodiment, the description will be omitted or simplified as appropriate for the same or corresponding parts. The present invention is not limited to the embodiments described below, and various modifications can be made as needed. For example, the embodiments described below may be partially implemented.

Embodiment 1.
The present embodiment will be described with reference to FIGS. 1 to 5.

*** Explanation of configuration ***
The configuration of the log management system 100 according to the present embodiment will be described with reference to FIG.

The log management system 100 includes a management device 200 that assigns an identifier as a group ID, and a plurality of server devices 300 that execute individual processes in cooperation with each other. "ID" is an abbreviation for Identifier.

The management device 200 and each server device 300 communicate with each other via a network such as the Internet (not shown). The server devices 300 communicate with each other via a network such as a LAN (not shown). "LAN" is an abbreviation for Local Area Network.

The configuration of the management device 200 according to the present embodiment will be described with reference to FIG.

The management device 200 is a computer. Specifically, the management device 200 is a server computer such as a cloud server. The management device 200 includes a processor 201 and other hardware such as a memory 202 and a communication device 203. The processor 201 is connected to other hardware via a signal line and controls these other hardware.

The management device 200 includes a receiving unit 210, a first transmitting unit 211, and a second transmitting unit 212 as functional elements. The functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 are realized by software. Specifically, the functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 are realized by the management program. The management program is a program that causes a computer to execute the procedures performed by the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 as a receiving procedure, a first transmitting procedure, and a second transmitting procedure, respectively. The management program may be recorded and provided on a computer-readable medium, may be stored and provided on a recording medium, or may be provided as a program product.

The processor 201 is a device that executes a management program. The processor 201 is, for example, a CPU. "CPU" is an abbreviation for Central Processing Unit.

The memory 202 is a device that stores a management program in advance or temporarily. The memory 202 is, for example, a RAM, a flash memory, or a combination thereof. "RAM" is an abbreviation for Random Access Memory.

The communication device 203 includes a receiver that receives data input to the management program and a transmitter that transmits data output from the management program. The communication device 203 is, for example, a communication chip or a NIC. "NIC" is an abbreviation for Network Interface Card.

The management device 200 may include an input device and a display as hardware.

An input device is a device operated by a user to input data into a management program. The input device is, for example, a mouse, a keyboard, a touch panel, or a combination of some or all of them.

A display is a device that displays data output from a management program on a screen. The display is, for example, an LCD. "LCD" is an abbreviation for Liquid Crystal Display.

The management program is read from the memory 202 into the processor 201 and executed by the processor 201. Not only the management program but also the OS is stored in the memory 202. The processor 201 executes the management program while executing the OS. A part or all of the management program may be incorporated in the OS.

The management program and the OS may be stored in the auxiliary storage device. The auxiliary storage device is, for example, an HDD, a flash memory, or a combination thereof. "HDD" is an abbreviation for Hard Disk Drive. When stored in the auxiliary storage device, the management program and the OS are loaded into the memory 202 and executed by the processor 201.

The management device 200 may include a plurality of processors that replace the processor 201. These multiple processors share the execution of the management program. Each processor is, for example, a CPU.

Data, information, signal values and variable values used, processed or output by the management program are stored in the memory 202, the auxiliary storage device, or the register or cache memory in the processor 201. In this embodiment, at least the related event setting file 220, the count number 221 and the reset number 222 are stored in the memory 202.

The management device 200 may be composed of one computer or a plurality of computers. When the management device 200 is composed of a plurality of computers, the functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 may be distributed and realized in each computer.

The configuration of the server device 300 according to the present embodiment will be described with reference to FIG.

The server device 300 is a computer. Specifically, the server device 300 is a server computer such as a web server, an application server, or a database server. The server device 300 includes a processor 301 and other hardware such as a memory 302 and a communication device 303. The processor 301 is connected to other hardware via a signal line and controls these other hardware.

The server device 300 includes a transmission unit 310, a first reception unit 311 and a second reception unit 312, and an execution unit 313 as functional elements. The functions of the transmission unit 310, the first reception unit 311 and the second reception unit 312 and the execution unit 313 are realized by software. Specifically, the functions of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 are realized by the server program. The server program is a program that causes a computer to execute the procedures performed by the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 as a reception procedure, a first transmission procedure, and a second transmission procedure, respectively. The server program may be recorded and provided on a computer-readable medium, may be stored and provided on a recording medium, or may be provided as a program product.

The processor 301 is a device that executes a server program. The processor 301 is, for example, a CPU.

The memory 302 is a device that stores a server program in advance or temporarily. The memory 302 is, for example, a RAM, a flash memory, or a combination thereof.

The communication device 303 includes a receiver that receives data input to the server program and a transmitter that transmits data output from the server program. The communication device 303 is, for example, a communication chip or a NIC.

The server device 300 may include an input device and a display as hardware.

An input device is a device operated by a user to input data into a server program. The input device is, for example, a mouse, a keyboard, a touch panel, or a combination of some or all of them.

A display is a device that displays data output from a server program on a screen. The display is, for example, an LCD.

The server program is read from memory 302 into processor 301 and executed by processor 301. Not only the server program but also the OS is stored in the memory 302. The processor 301 executes the server program while executing the OS. A part or all of the server program may be incorporated in the OS.

The server program and the OS may be stored in the auxiliary storage device. The auxiliary storage device is, for example, an HDD, a flash memory, or a combination thereof. When stored in the auxiliary storage device, the server program and the OS are loaded into the memory 302 and executed by the processor 301.

The server device 300 may include a plurality of processors that replace the processor 301. These plurality of processors share the execution of the server program. Each processor is, for example, a CPU.

Data, information, signal values and variable values used, processed or output by the server program are stored in the memory 302, the auxiliary storage device, or the register or cache memory in the processor 301. In this embodiment, at least the log file 320 is stored in the memory 302.

The server device 300 may be composed of one computer or a plurality of computers. When the server device 300 is composed of a plurality of computers, the functions of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 may be distributed and realized in each computer. ..

*** Explanation of operation ***
The operation of the log management system 100 according to the present embodiment will be described with reference to FIG. The operation of the log management system 100 corresponds to the log management method according to the present embodiment.

In this embodiment, in a system in which a plurality of server devices 300 operate in cooperation with each other, related events such as "transmission" and "reception" executed by each server device 300 are grouped. The same group ID is assigned to related events.

The management device 200 is arranged as a server for assigning the group ID. The management device 200 receives a request from each server device 300 and returns a group ID. The management device 200 holds the setting information of the name and order of the related events included in the group as the related event setting file 220, assigns the group ID to each server device 300, and at the same time instructs the transmission thereof.

The assignment of the group ID and the transmission between the server devices 300 are realized by the following procedure.

The procedure depends on whether the event to be executed is first, middle, or last in the related group.

The case of executing the three related events "start", "cmd1", and "cmd2" will be described as an example.

In step S11, the server A, which is the server device 300 that executes the first process A, requests the management device 200 for the group ID. At that time, the server A also notifies the event name to be granted. Here, "start" is notified as an example. Note that the server A holds in advance a file that defines the correspondence between the type of processing to be executed and the event name, and when requesting the group ID, the event name to be notified by referring to this file. Suppose you get a "start".

In step S12, the management device 200 refers to the related event setting file 220 to check whether the event for which the group ID is requested is registered as a group and the number of the event to be executed. The management device 200 recognizes that the event "start" is registered as "Group1", is executed first, and has the next event.

In step S13, since the event "start" is executed first and there is the next event, the management device 200 returns the group ID and "next" to the server A.

In step S14, the server A receives the "next" and transmits the group ID in the form of being embedded in the command "cmd1" to the server B which is the next server device 300.

In step S15, the server B, which is the server device 300 that executes the process B in the middle, requests the management device 200 for the group ID. At that time, the server B also notifies the event name to be granted. Here, "cmd1" is notified as an example. Note that the server B holds in advance a file that defines the correspondence between the type of processing to be executed and the event name, and when requesting the group ID, the event name to be notified by referring to this file. It is assumed that "cmd1" is obtained.

In step S16, the management device 200 refers to the related event setting file 220, recognizes that the event "cmd1" is registered as "Group1", is executed second, and has the next event.

In step S17, the management device 200 returns "prev" and "next" to the server B because the event "cmd1" is not the first event but the next event. The server B receives the "prev" and acquires the group ID from the command "cmd1" from the server A which is the server device 300 immediately before.

In step S18, the server B receives the "next" and transmits the group ID in the form of being embedded in the command "cmd2" to the server C which is the next server device 300. In a situation where it is not necessary to operate the server C, the server B may ignore "next". That is, even if the server B receives the "next", it may independently determine whether or not to transmit the group ID to the server C.

In step S19, the server C, which is the server device 300 that executes the final process C, requests the management device 200 for the group ID. At that time, the server C also notifies the event name to be granted. Here, "cmd2" is notified as an example. The server C holds in advance a file that defines the correspondence between the type of processing to be executed and the event name, and when requesting the group ID, the event name to be notified by referring to this file. It is assumed that "cmd2" is obtained.

In step S20, the management device 200 refers to the related event setting file 220, recognizes that the event "cmd2" is registered as "Group1", is executed third, and there is no next event.

In step S21, the management device 200 returns "prev" and "none" to the server C because the event "cmd2" is not the first event and there is no next event. The server C receives the "prev" and acquires the group ID from the command "cmd2" from the server B which is the server device 300 immediately before.

The processing procedure of the management device 200 will be described with reference to FIG.

In step S31, the management device 200 reads the related event setting file 220.

In step S32, the management device 200 receives the group ID request.

In step S33, the management device 200 determines the return value.

In step S34, the management device 200 transmits the return value to the requesting server device 300.

There are a value 1 and a value 2 as the return value.

The value 1 is the group ID newly assigned to the event if the event notified by the group ID request is the first event, and the group ID transmitted from the immediately preceding server device 300 other than the first event. It becomes "prev" instructing to use. The numbering of the group ID will be described later.

The value 2 is "none" instructing the next server device 300 not to transmit the group ID if the event notified by the group ID request is the last event, and if it is other than the last event, the group is sent to the next server device 300. It becomes "next" instructing to transmit the ID.

In the present embodiment, a numerical value in which the date, the reset number 222, and the count number 221 are arranged as shown in FIG. 5 is used as the group ID. As an example, if the date is "February 14, 2018", the reset number 222 is "0", and the count number 221 is "1", the group ID is "2018021400001".

The group ID starts with the date and the count number 221 is returned to "0" every 24 hours in order to prevent the value from becoming infinitely large. The digit of the reset number 222 is provided assuming that a failure occurs in the management device 200 and the count number 221 reaches the maximum value, and the group ID does not overlap even if the count number 221 is reset on the same day. The mechanism is adopted. The reset number 222 is recorded in a file in the management device 200 and is inherited even if the management device 200 is restarted, but returns to "0" when the day changes. The count number 221 has four digits by default, but if there are many logs generated by each server device 300, the number of digits may be increased.

Since a common group ID is used by each server device 300, it is necessary to transmit the group ID between the server devices 300. In the present embodiment, the group ID is transmitted in a form of being embedded in an event instruction to the next server device 300. Specifically, the group ID is embedded as an argument of the URL when transmitted to an application server such as Tomcat. "URL" is an abbreviation for Uniform Resource Locator. When the group ID is transmitted to a database server such as Oracle (registered trademark), it is embedded as a comment of SQL.

The operation of each part of the management device 200 and the server device 300 will be described with reference to FIGS. 1 to 3.

In step S11, the transmission unit 310 of the server A, which is the server device 300 that executes the process A in cooperation with the other server devices 300 such as the server B and the server C, requests to notify the type of the process A as an event "start". The data 400 is transmitted to the management device 200.

In step S12, the receiving unit 210 of the management device 200 receives the request data 400 notifying the type of the process A executed by the server A as the event "start" from the server A. The first transmission unit 211 of the management device 200 is classified into the same group in the related event setting file 220 stored in the memory 202, and is the first event "start" in a series of events in which the order in the group is defined. It is recognized that the data notifying "" has been received by the receiving unit 210 as the request data 400.

In step S13, the first transmission unit 211 of the management device 200 assigns a group ID, and transmits the first response data 401 including the assigned group ID to the server A, which is the server device 300 that is the source of the request data 400. .. In the present embodiment, the first transmission unit 211 is another server device 300 that includes the assigned group ID and executes the assigned group ID in the next process B of the process A executed by the server A. The server B is instructed to notify, that is, the data including "next" is transmitted as the first response data 401.

When assigning the group ID, the first transmission unit 211 includes the information on the date and time when the group ID is assigned in the group ID to be assigned. Specifically, the first transmission unit 211 arranges the date at the beginning of the group ID to be assigned. Further, the first transmission unit 211 includes the count number 221 stored in the memory 202 in the group ID to be assigned, and then increments the count number 221 stored in the memory 202. Specifically, the first transmission unit 211 arranges the count number 221 stored in the memory 202 at the end of the group ID to be assigned, and then increments the count number 221 stored in the memory 202 by one. Further, the first transmission unit 211 includes the reset number 222 stored in the memory 202 in the group ID to be assigned. Specifically, the first transmission unit 211 arranges the reset number 222 stored in the memory 202 between the date of the group ID to be assigned and the count number 221. When the count number 221 stored in the memory 202 has reached the maximum value, the first transmission unit 211 resets the count number 221 stored in the memory 202 to an initial value instead of incrementing the count number 221 and stores the count number 221 in the memory 202. The reset number 222 is incremented. Specifically, when the count number 221 stored in the memory 202 reaches "9999", the first transmission unit 211 resets the count number 221 stored in the memory 202 to "0" instead of incrementing it by 1. At the same time, the reset number 222 stored in the memory 202 is incremented by 1.

The first transmission unit 211 resets the count number 221 and the reset number 222 stored in the memory 202 to the initial values when the date changes. Specifically, the first transmission unit 211 resets the count number 221 and the reset number 222 stored in the memory 202 to "0" when the date changes.

In step S14, the first receiving unit 311 of the server A receives the first response data 401 including the group ID assigned by the management device 200 from the management device 200. In the present embodiment, the first receiving unit 311 includes the group ID given by the management device 200, and instructs the server B to notify the given group ID, that is, the data including "next". Received as the first response data 401. Therefore, the transmission unit 310 of the server A transmits the call data 403 notifying the group ID included in the first response data 401 to the server B.

The execution unit 313 of the server A executes the process A and outputs a log recording the group ID included in the first response data 401 to the log file 320.

In step S15, the transmission unit 310 of the server B, which is the server device 300 that executes the process B in cooperation with the other server devices 300 such as the server A and the server C, requests to notify the type of the process B as the event "cmd1". The data 400 is transmitted to the management device 200.

In step S16, the receiving unit 210 of the management device 200 receives the request data 400 notifying the type of the process B executed by the server B as the event “cmd1” from the server B. The second transmission unit 212 of the management device 200 is classified into the same group in the related event setting file 220 stored in the memory 202, and is the second and subsequent events in a series of events whose order is defined in the group. It recognizes that the data notifying "cmd1" has been received by the receiving unit 210 as the request data 400. In the present embodiment, the second transmission unit 212 is classified into the same group in the related event setting file 220 stored in the memory 202, and the second and subsequent events in the series in which the order in the corresponding group is defined. It recognizes that the data notifying the event "cmd1" other than the last is received by the receiving unit 210 as the request data 400.

In step S17, the second transmission unit 212 of the management device 200 is the server device 300 of the source of the request data 400 for the second response data 402 instructing to use the group ID assigned by the first transmission unit 211. Send to server B. Specifically, the second transmission unit 212 instructs to use the group ID notified from the server A, which is another server device 300 that executes the process A before the process B executed by the server B. That is, the data including "prev" is transmitted as the second response data 402. In the present embodiment, the second transmission unit 212 instructs to use the group ID notified from the server A, and sets the notified group ID to the next process C of the process B executed by the server B. The server C, which is another server device 300 to be executed, is instructed to notify, that is, the data including "next" is transmitted as the second response data 402.

In step S18, the second receiving unit 312 of the server B receives the second response data 402 instructing to use the group ID assigned by the management device 200 from the management device 200, and also receives the second response data 402 instructing to use the group ID assigned by the management device 200 from the management device 200. The call data 403 notifying the group ID assigned by 200 is received. In the present embodiment, the second receiving unit 312 instructs to use the group ID notified from the server A, that is, includes "prev" and instructs the server C to notify the notified group ID. That is, the data including "next" is received as the second response data 402. Therefore, the transmission unit 310 of the server B generates another call data 403 notifying the group ID notified by the call data 403 from the server A, and transmits the generated call data 403 to the server C. If there is no next process of process B, the transmission unit 310 does not have to generate or transmit the call data 403.

The execution unit 313 of the server B executes the process B and outputs a log recording the group ID notified by the call data 403 to the log file 320.

In step S19, the transmission unit 310 of the server C, which is the server device 300 that executes the process C in cooperation with the other server devices 300 such as the server A and the server B, requests to notify the type of the process C as the event "cmd2". The data 400 is transmitted to the management device 200.

In step S20, the receiving unit 210 of the management device 200 receives the request data 400 notifying the type of the process C executed by the server C as the event "cmd2" from the server C. The second transmission unit 212 of the management device 200 is classified into the same group in the related event setting file 220 stored in the memory 202, and is the second and subsequent events in a series of events whose order is defined in the group. It recognizes that the data notifying "cmd2" has been received by the receiving unit 210 as the request data 400. In the present embodiment, the second transmission unit 212 is classified into the same group in the related event setting file 220 stored in the memory 202, and is the last event "of a series of events in which the order in the corresponding group is defined. It recognizes that the data notifying "cmd2" has been received by the receiving unit 210 as the request data 400.

In step S21, the second transmission unit 212 of the management device 200 is the server device 300 of the source of the request data 400 for the second response data 402 instructing to use the group ID assigned by the first transmission unit 211. Send to server C. Specifically, the second transmission unit 212 instructs to use the group ID notified from the server B, which is another server device 300 that executes the process B before the process C executed by the server C. That is, the data including "prev" is transmitted as the second response data 402. In the present embodiment, the second transmission unit 212 instructs to use the group ID notified from the server B, and notifies that it is not necessary to notify the other server device 300 of the notified group ID. That is, the data including "none" is transmitted as the second response data 402.

The second receiving unit 312 of the server C receives the second response data 402 instructing to use the group ID assigned by the management device 200 from the management device 200, and has already been assigned by the management device 200 from the server B. Receives the call data 403 notifying the group ID of. In the present embodiment, the second receiving unit 312 instructs to use the group ID notified from the server B, that is, includes "prev" and does not have to notify the notified group ID. Notify, that is, receive the data including "none" as the second response data 402.

The execution unit 313 of the server C executes the process C and outputs a log recording the group ID notified by the call data 403 to the log file 320.

The group ID may be in any format as long as a series of events can be identified as one group, and the date, reset number 222, or both of them may not be included as a modification.

An application example of this embodiment will be described with reference to FIGS. 6 and 7.

The event grouping will be described by taking as an example a log management system 100 in which a web server such as Apache (registered trademark), an application server such as Tomcat, and a database server such as Oracle (registered trademark) are combined as the server device 300.

In this example, the web client accesses the web server. The web server calls an application such as Java® on the application server. The application server runs the application and the application calls the database server. The database server performs the search and returns the search results to the application server. Each server device 300 requests a group ID from the management device 200.

In the related event setting file 220 on the management device 200, "Group1 = WebAccess, AppExec, DBSearch" is set.

In step S41, the web client refers to the web server. In step S42, the web server requests the management device 200 for the "web access" group ID. In step S43, the management device 200 refers to the related event setting file 220, and the event name "Web Access" of "Web Access" is registered as a process in the group, which is the first process to be executed and Since there is the next processing, the group ID "2018021400001" is generated and "GID = 2018021400001, next" is returned. In step S44, the web server outputs a log including the group ID "2018021400001" to the log file 320. In step S45, the web server sends an application execution instruction to the application server. At this time, the web server receives the next instruction of the management device 200 and embeds the group ID "2018021400001" in the instruction.

In step S46, the application server executes the application. In step S47, the application server requests the management device 200 for the group ID of "application execution". In step S48, the management device 200 refers to the related event setting file 220, and the event name "AppExec" of "application execution" is registered as a process in the group, which is the second process to be executed and Since there is the next processing, "GID = prev, next" is returned. In step S49, the application server receives the prev instruction and acquires the group ID "2018021400001" from the application execution instruction. In step S50, the application server outputs a log including the group ID "2018021400001" to the log file 320. In step S51, the application server sends a database search command to the database server. At this time, the application server receives the next instruction of the management device 200 and embeds the group ID "2018021400001" in the instruction.

In step S52, the database server performs the search. In step S53, the database server requests the management device 200 for the group ID of "database search". In step S54, the management device 200 refers to the related event setting file 220, and the event name “DBSearch” of “database search” is registered as a process in the group, which is the third process to be executed and Since there is no next process, "GID = prev, one" is returned. In step S55, the database server receives the prev instruction and acquires the group ID "2018021400001" from the database search instruction. In step S56, the database server outputs a log including the group ID "2018021400001" to the log file 320. In step S57, the database server returns the database search result to the application. In step S58, the application server returns the application execution result to the web server. In step S59, the web server returns the web screen data to the web client.

*** Explanation of the effect of the embodiment ***
In the present embodiment, a series of processes executed in cooperation between the servers are grouped by an identifier. Therefore, according to the present embodiment, these series of processes can be clearly associated with each other.

In the present embodiment, by grouping the events that occur in each server device 300, it is possible to grasp the association of a series of processes. That is, in the present embodiment, the concept of "group ID" is introduced, a group ID is assigned to each server device 300 from the management device 200, and related events are grouped to be different from the system time. Information can be used in common by all servers, and a series of operations executed between the server devices 300 can be clearly associated with each other.

As a specific example, the relationship and order of a series of operations between servers will be clarified, and it will be easier to identify the problem area when a failure occurs. Conventionally, when it is desired to check the processing result of a series of operations for failure resolution, it is necessary to follow the log of each server in order depending on the execution time, but in the present embodiment, the processing in which the failure has occurred. If you know the group ID of, you can check the log of any server.

Moreover, even if the system time deviates, confusion does not occur because the order and relationship of each operation is clear. Conventionally, it is necessary to check the log while considering the deviation of the system time of each server, and a judgment error is likely to occur. However, in the present embodiment, it is sufficient to check the log of the same group ID, so the judgment is made. It is hard to make mistakes.

In addition, it becomes easy to determine the execution order of the processes started on the two servers. In the past, it was necessary to compare the execution times on each server while considering the difference in system time, and if the processes were executed on the two servers at almost the same time, the execution times would be the same and the execution order could not be determined. In the present embodiment, the magnitude of the assigned group ID is the execution order as it is, so it is only necessary to compare the sizes of the group ID. Even when the processes are executed almost at the same time, the execution order can be determined because the individual group IDs are assigned.

*** Other configurations ***
In the present embodiment, the functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 of the management device 200 are realized by software, but as a modification, the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 are realized. 2. The function of the transmitter 212 may be realized by dedicated hardware. Alternatively, as another modification, the functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 may be realized by a combination of software and hardware. That is, a part of the functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 may be realized by dedicated hardware, and the rest may be realized by software.

Dedicated hardware is, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an FPGA, an ASIC, or some or a combination of all of these. .. "IC" is an abbreviation for Integrated Circuit. "GA" is an abbreviation for Gate Array. "FPGA" is an abbreviation for Field-Programmable Gate Array. "ASIC" is an abbreviation for Application Special Integrated Circuit.

Both the processor 201 and the dedicated hardware are processing circuits. That is, regardless of whether the functions of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 are realized by software, hardware, or a combination of software and hardware. The operations of the receiving unit 210, the first transmitting unit 211, and the second transmitting unit 212 are performed by the processing circuit.

In the present embodiment, the functions of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 of the server device 300 are realized by software, but as a modification, the transmission unit 310 and the first reception unit The functions of the unit 311, the second receiving unit 312, and the executing unit 313 may be realized by dedicated hardware. Alternatively, as another modification, the functions of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 may be realized by a combination of software and hardware. That is, a part of the functions of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 may be realized by dedicated hardware, and the rest may be realized by software.

Dedicated hardware is, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an FPGA, an ASIC, or some or a combination of all of these. ..

Both the processor 301 and the dedicated hardware are processing circuits. That is, the functions of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 are realized by software, hardware, or a combination of software and hardware. Regardless of this, the operations of the transmission unit 310, the first reception unit 311, the second reception unit 312, and the execution unit 313 are performed by the processing circuit.

100 log management system, 200 management device, 201 processor, 202 memory, 203 communication device, 210 receiver, 211 first transmitter, 212 second transmitter, 220 related event setting file, 221 count number, 222 reset number, 300 Server device, 301 processor, 302 memory, 303 communication device, 310 transmitter, 311 first receiver, 312 second receiver, 313 execution unit, 320 log file, 400 request data, 401 first response data, 402 second Response data, 403 call data.

Claims (14)

A receiver that receives request data that notifies the type of processing executed by each server device as an event from multiple server devices that execute individual processes in cooperation with each other.
When the data for notifying the first event of a series of events classified into the same group in the setting information stored in the memory and the order in the corresponding group is defined is received by the receiving unit as the request data. A first transmission unit that assigns an identifier to the server and transmits the first response data including the assigned identifier to the server device that is the source of the request data.
When the data notifying the second and subsequent events in the series of events is received by the receiving unit as the request data, the second response instructing to use the identifier given by the first transmitting unit. A management device including a second transmission unit that transmits data to a server device that transmits the request data. The first transmission unit includes the assigned identifier, and instructs other server devices that execute the next process of the process executed by the server device that transmits the request data to notify the assigned identifier. The data is transmitted as the first response data,
The second response data is data instructing the second transmission unit to use an identifier notified from another server device that executes a process before the process executed by the server device that is the source of the request data. The management device according to claim 1, which is transmitted as. When the data for notifying the second and subsequent events other than the last of the series of events is received by the receiving unit as the request data, the second transmitting unit is the server device of the source of the request data. Instructs to use the identifier notified from the other server device that executes the process before the process executed in, and the notified identifier is the process executed by the server device that sends the request data. The management device according to claim 2, wherein data instructing another server device that executes the next process to be notified is transmitted as the second response data. The management device according to any one of claims 1 to 3, wherein the first transmission unit includes information on the date and time when an identifier is assigned in the identifier to be assigned. The management device according to any one of claims 1 to 4, wherein the first transmission unit includes a count number stored in the memory in an identifier to be assigned, and then increments the count number stored in the memory. The management device according to claim 5, wherein the first transmission unit resets the count number stored in the memory to an initial value when the date changes. The first transmission unit includes the count number stored in the memory and the reset number stored in the memory in the identifier to be assigned, and when the count number stored in the memory reaches the maximum value, the memory The management device according to claim 5 or 6, wherein the count number stored in the memory is reset to an initial value instead of being incremented, and the reset number stored in the memory is incremented. The management device according to claim 7, wherein the first transmission unit resets the reset number stored in the memory to an initial value when the date changes. In a server device that executes processing in cooperation with other server devices
A transmission unit that transmits request data for notifying the type of processing as an event to a management device to which an identifier is assigned.
When the data for notifying the first event of a series of events classified into the same group and the order in the corresponding group is defined is transmitted as the request data by the transmission unit, the management device can display the data. A first receiving unit that receives the first response data including the identifier given by the management device, and
When the data notifying the second and subsequent events in the series of events is transmitted by the transmission unit as the request data, the management device instructs the management device to use the identifier given by the management device. A second receiving unit that receives the second response data and also receives the call data notifying the identifier assigned by the management device from another server device that executes the process before the process.
When the first response data is received by the first receiving unit, the process is executed and a log recording an identifier included in the first response data is output, and the second response data is the second response data. (2) A server device including an execution unit that executes the process and outputs a log recording an identifier notified by the call data when the data is received by the reception unit. The first receiving unit includes the identifier given by the management device, and sends data instructing the other server device that executes the next process of the process to notify the assigned identifier to the first response. Received as data
When the first response data is received by the first receiving unit, the transmitting unit executes the call data notifying the identifier included in the first response data to the next processing of the processing. The server device according to claim 9, which is transmitted to the server device. When the second response data is received by the second receiving unit, the transmitting unit generates another calling data notifying the identifier notified by the calling data if there is a next processing of the processing. The server device according to claim 9 or 10, wherein the generated call data is transmitted to another server device that executes the next process of the process. Multiple server devices that execute individual processes in cooperation with each other send request data that notifies the type of process executed by each server device as an event to the management device that assigns an identifier.
When the management device receives data notifying the first event of a series of events classified into the same group and whose order is defined in the group as the request data, an identifier is assigned. The first response data including the assigned identifier is transmitted to the server device that is the source of the request data, and the data is transmitted.
When each server device receives the first response data, the processing of each server device is executed, and a log recording the identifier included in the first response data is output.
When the management device receives data notifying the second and subsequent events in the series of events as the request data, the second response data instructing the management device to use the identifier assigned by the management device is provided. It is transmitted to the server device that is the source of the request data, and
When each server device receives the second response data, it receives call data notifying the identifier given by the management device from another server device that executes the processing before the processing of each server device. , A log management method that executes the processing of each server device and outputs a log recording the identifier notified by the call data. On the computer
A reception procedure for receiving request data that notifies the type of processing executed by each server device as an event from multiple server devices that execute individual processes in cooperation with each other.
When the data notifying the first event of a series of events classified into the same group in the setting information stored in the memory and the order in the corresponding group is defined is received as the request data by the reception procedure. The first transmission procedure of assigning an identifier to the server and transmitting the first response data including the assigned identifier to the server device that is the source of the request data.
When the data notifying the second and subsequent events in the series of events is received as the request data by the receiving procedure, the second response instructing to use the identifier given by the first transmitting procedure. A management program that executes a second transmission procedure for transmitting data to a server device that transmits the request data. To a computer that is a server device that executes processing in cooperation with other server devices
A transmission procedure for transmitting request data for notifying the type of processing as an event to a management device to which an identifier is assigned, and
When the data notifying the first event of a series of events classified into the same group and the order in the corresponding group is defined is transmitted as the request data by the transmission procedure, the management device can display the data. The first receiving procedure for receiving the first response data including the identifier given by the management device, and
When the data notifying the second and subsequent events in the series of events is transmitted as the request data by the transmission procedure, the management device instructs the management device to use the identifier given by the management device. A second reception procedure for receiving the second response data and receiving call data notifying the identifier assigned by the management device from another server device that executes the process before the process.
When the first response data is received by the first reception procedure, the process is executed and a log recording the identifier included in the first response data is output, and the second response data is the first response data. (2) A server program that, when received by the receiving procedure, executes the processing and also executes the execution procedure of outputting a log recording the identifier notified by the calling data.

Images