JP7338246B2 - Information processing device, log reference program - Google Patents

Description

The present invention relates to an information processing device and a log reference program.

Conventionally, it is known to build a system using a technology called microservice architecture. In a microservices architecture, software that provides a single service is divided into multiple smaller applications called components. A component execution unit is called a container.

JP 2018-136681 A JP 2018-097793 A

In the conventional system, each of the container, the OS (Operating System) of the virtual machine on which the container is operating, and the OS of the physical machine on which the virtual machine is operating individually outputs log data. Also, in conventional systems, containers migrate between OSs. For this reason, in the conventional system, it is difficult to specify log data to be referred from among a large number of OS log data, for example, when investigating a failure that has occurred in a container.

In one aspect, an object of the present invention is to identify log data to be referred to.

In one aspect, a data acquisition unit that collects a migration log indicating a history of movement of a container, and an operation related to the container by referring to the migration log when a part of the execution log of the container is selected. The information processing apparatus includes log data of a system and a log identification unit that identifies the position of the container.

Each part described above may be a process for realizing each part, a procedure for realizing each part, or a computer-readable storage medium storing a program for causing a computer to execute each process.

It is possible to identify the log data that should be referenced.

It is a figure which shows an example of the system configuration|structure of an information processing system. It is a figure which shows an example of the hardware constitutions of a server apparatus. It is a figure explaining the function of each apparatus which an information processing system has. It is a figure explaining a processing result database. FIG. 4 is a diagram showing an example of a migration log database; FIG. It is a figure which shows an example of a normal state database. It is a figure which shows an example of a performance database. It is a figure which shows an example of a log database. 4 is a flowchart for explaining processing of a container data collection unit of the information processing device; 7 is a flowchart for explaining processing of a virtual machine data collection unit of an information processing device; FIG. 10 is a diagram showing an example of a container position table when a decrease in containers is detected; FIG. 10 is a diagram showing an example of a virtual machine location table when an increase in virtual machines is detected; 4 is a flowchart for explaining processing of a performance data collection unit; FIG. 10 is a flowchart for explaining processing of a log reference processing unit of the server device; FIG. It is a figure explaining comparison of process result data and normal state data. It is a figure which shows an example of intermediate data. It is a figure which shows an example of a performance database at the time of abnormality. It is a figure which shows the example of a display of log data.

A first embodiment will be described below with reference to the drawings. FIG. 1 is a diagram showing an example of the system configuration of an information processing system.

The information processing system 100 of this embodiment includes a server device 200 and information processing devices 300-1, . . . , 300-N.

Each of the information processing apparatuses 300-1, . In the following description, the information processing devices 300-1, . Also, in the following description, the information processing device 300 may be referred to as a physical machine 300. FIG.

In the information processing apparatus 300 of this embodiment, an OS (Operating System) 310 serving as a host is executed, and a hypervisor 320 operates on the OS 310 . Hypervisor 320 manages a plurality of virtual machines 330-1, . In the following description, the plurality of virtual machines 330-1, .

The virtual machine 330 executes an OS 331 as a guest. In the virtual machine 330, the container management unit 334 operates a plurality of applications on the OS 331 in different environments having independent process spaces and name spaces. Different environments for multiple applications are containers 332-1, . . . , 332-N.

Each of the plurality of containers 332-1, . . . , 332-N migrates between the OSs 331 of the virtual machines 330-1, .

Also, the plurality of containers 332-1, . . . , 332-N communicate with other containers via a plurality of proxies 333-1, . In the following description, the plurality of containers 332-1, . If not, it is called proxy 333 .

In the information processing device 300, the OS 310 of the information processing device 300, the OS 331 of the virtual machine 330, and the container 332 operating on each virtual machine 330 each output log data. The server device 200 collects these log data.

In addition, the server device 200 of the present embodiment receives from the information processing device 300 the corresponding relationship (association) among the container 332, the virtual machine 330, and the physical machine (information processing device) 300, and the time at which each was associated. Acquire the correspondence information indicating the .

In the present embodiment, by acquiring this association information, it is possible to specify the log data of the OS related to the container 332 in which the failure occurred when investigating the failure that occurred in the container. In other words, in this embodiment, log data to be referred to can be specified when a failure occurs in the container 332 .

The server apparatus 200 of this embodiment has a processing result database 210 , a migration log database 220 , a normal state database 230 , a performance database 240 , a log database 250 , an abnormal performance database 260 and an abnormal log database 270 . Further, the server device 200 of this embodiment has a log reference processing unit 280 .

The processing result database 210 stores data resulting from analyzing the log data of the container 332 acquired via the proxy 333 . In other words, the processing result database 210 stores processing result data obtained by analyzing execution log data of processing by the container 332 .

The migration log database 220 stores correspondence information indicating the correspondence between the container 332, the virtual machine 330, and the physical machine (information processing device) 300, and the time at which they were associated. In other words, the migration log database 220 contains information indicating the virtual machine 330 on which the container 332 was running, the time when the container 332 was running, the information processing device 300 on which the virtual machine 330 was running, Information indicating the time when the virtual machine 330 was operating is stored.

The normal state database 230 stores normal state data that is referred to when determining whether or not processing by the container 332 has been performed normally.

The performance database 240 stores performance data indicating the performance of the information processing device 300 and performance data indicating the performance of the virtual machine 330 . The log database 250 stores log data for each of the OS 310 , OS 331 and container 332 .

The abnormal performance database 260 stores performance data of the information processing device 300 and the virtual machine 330 when the processing result data obtained by analyzing the container log data is not in the state indicated by the normal state data.

The abnormal log database 270 stores log data of each of the OS 310, OS 331, and container 332 when the processing result data obtained by analyzing the container log data is not in the state indicated by the normal state data.

The log reference processing unit 280 collects log data, analyzes the log data, manages correspondence information between the information processing device 300, the virtual machine 330, and the container 332, and determines whether the log data acquired from the container 332 is normal. Processing such as judgment is performed.

In this embodiment, the processing result database 210, the migration log database 220, the normal state database 230, the performance database 240, the log database 250, the abnormal performance database 260, and the abnormal log database 270 are provided in the server device 200. However, it is not limited to this.

For example, the abnormal performance database 260 and the abnormal log database 270 may be provided in a device other than the server device 200 . More specifically, the abnormal-time performance database 260 and the abnormal-time log database 270 may be provided, for example, in an investigation server device or the like that is referred to when conducting an investigation when a failure occurs. In this embodiment, the data stored in the abnormal performance database 260 and the abnormal log database 270 are retained for a sufficiently long period compared to the data stored in the performance database 240 and the log database 250 .

Also, all databases shown in FIG. 1 may be provided in a device other than the server device 200 .

Next, with reference to FIG. 2, the hardware configuration of the server device 200 of this embodiment will be described. FIG. 2 is a diagram illustrating an example of a hardware configuration of a server device;

The server device 200 of this embodiment has an input device 21, an output device 22, a drive device 23, an auxiliary storage device 24, a memory device 25, an arithmetic processing device 26, and an interface device 27, which are connected to each other via a bus B. It is an information processing device.

The input device 21 is, for example, a keyboard, pointing device, etc., and inputs various kinds of information. The output device 22 is, for example, a display, and outputs various information. The interface device 27 is used for connecting to the network.

A log reference program that implements the log reference processing unit 280 is at least part of various programs that control the server device 200 . The log reference program is provided, for example, by distribution of the recording medium 28 or download from a network. The recording medium 28 in which the log reference program is recorded is a recording medium for optically, electrically or magnetically recording information such as a CD-ROM, a flexible disk, a magneto-optical disk, or a recording medium such as a ROM or a flash memory. Various types of recording media can be used, such as a semiconductor memory that electrically records .

Further, the log reference program is installed in the auxiliary storage device 24 from the recording medium 28 via the drive device 23 when the recording medium 28 recording the log reference program is set in the drive device 23 . A log reference program downloaded from the network is installed in the auxiliary storage device 24 via the interface device 27 .

The auxiliary storage device 24 stores the installed log reference program, as well as various necessary files and data acquired by the server device 200 . The memory device 25 reads and stores the log reference program from the auxiliary storage device 24 when the server device 200 is started. The arithmetic processing unit 26 implements various processes described later according to the log reference program stored in the memory unit 25 .

The memory device 25 of this embodiment is, for example, a volatile memory and serves as an in-memory database of the server device 200 .

Note that the hardware configuration of the information processing device 300 is an information processing device having an arithmetic processing device and a memory device, and is the same as that of the server device 200, so a description thereof will be omitted.

Next, with reference to FIG. 3, the function of each device included in the information processing system 100 of this embodiment will be described. FIG. 3 is a diagram for explaining the function of each device included in the information processing system.

First, functions of the information processing apparatus 300 of this embodiment will be described. The information processing apparatus 300 of this embodiment has a virtual machine data collection unit 341 , a performance data collection unit 342 and a log data collection unit 343 .

The virtual machine data collection unit 341 collects a list of the virtual machines 330 existing on the information processing device (physical machine) 300 from the hypervisor 320 and the virtual machine position data associated with the time when the list is acquired. 200.

The virtual machine location data is information indicating the association (correspondence relationship) between the virtual machine 330 and the information processing device (physical machine) 300 and the associated time, and is stored in the migration log database 220 . That is, the virtual machine location data is part of the association information.

The performance data collection unit 342 collects performance data of each virtual machine 330 from the OS 310 and transmits the data to the server device 200 . The performance data includes, for example, CPU (Central Processing Unit) usage, memory usage, network usage, and the like. Also, the performance data collection unit 342 collects performance data of the information processing device 300 and transmits the data to the server device 200 .

The log data collection unit 343 collects log data of the OS 310 and transmits it to the server device 200 .

The virtual machine 330 of this embodiment has a container data collection unit 351 , a performance data collection unit 352 and a log data collection unit 353 .

The container data collection unit 351 transmits, from the container management unit 334 , the list of the containers 332 existing on the virtual machine 330 and the container position data in which the time at which the list was acquired are associated with each other to the server device 200 .

The container position data is information indicating the association (correspondence relationship) between the container 332 and the virtual machine 330 and the associated time, and is stored in the migration log database 220 . That is, the container position data is part of the correspondence information.

The performance data collection unit 352 collects performance data of each container 332 from the OS 331 and transmits it to the server device 200 . Performance data is stored in performance database 240 .

The log data collection unit 353 collects the log database of the OS 331 and the log data of the container 332 output via each proxy 333 and transmits them to the server device 200 . Log data is stored in the log database 250 . Further, the log data of the container 332 collected by the log data collection unit 353 is treated as processing result data by the log reference processing unit 280 and stored in the processing result database 210 .

Next, functions of the server device 200 will be described. The log reference processing unit 280 of the server device 200 of this embodiment includes a container data acquisition unit 281, a virtual machine data acquisition unit 282, a performance data acquisition unit 283, a log data acquisition unit 284, a log analysis unit 285, and a normal state data generation unit. 286 , a log identification unit 287 , a selection unit 288 and an output unit 290 .

The container data acquisition unit 281 acquires container position data collected by the container data collection unit 351 of the information processing device 300 and stores it in the migration log database 220 .

The virtual machine data acquisition unit 282 acquires virtual machine position data collected by the virtual machine data collection unit 341 of the information processing device 300 and stores it in the migration log database 220 .

The performance data acquisition unit 283 acquires the performance data collected by the performance data collection unit 342 and the performance data collected by the performance data collection unit 352 and stores them in the performance database 240 .

The log data acquisition unit 284 acquires the log data of the OS 310 collected by the log data collection unit 343, the log data of the OS 331 collected by the log data collection unit 353, and the log data of each container 332, and stores them in the log database 250. Store.

The log analysis unit 285 analyzes the log data of the container 332 acquired by the log data acquisition unit 284 and stores the processing result data of the analysis result in the processing result database 210 . The log analysis unit 285 also compares the processing result data with the normal state database 230 to determine whether the processing was executed normally. Details of the processing of the log analysis unit 285 will be described later.

The normal state data generation unit 286 generates normal state data based on the processing result data stored in the processing result database 210 and stores the normal state data in the normal state database 230 . Normal state data is data that is referred to when determining whether or not processing of the container 332 has been performed normally. The details of the processing of the normal state data generator 286 will be described later.

The log identification unit 287 refers to the migration log database 220, identifies the location of the container 332 that has executed the processing indicated by the processing result data, and logs and performance data of the OS 331 and the OS 310 associated with the location-identified container 332. and extract

Specifically, when the log analysis unit 285 determines that the process of the container 332 is not normally executed, the log identification unit 287 performs the processing of the container 332 that executed the process and the virtual machine 330 attached. Identify and extract the log data of the physical machine 300 . Then, the log identifying unit 287 adds information identifying the process that was not executed normally to the extracted performance data and log data, and stores the information in the abnormal performance database 260 and the abnormal log database 270, respectively.

The selection unit 288 accepts selection of part of the execution log of the container 332 . Specifically, the selection unit 288 receives selection of a request ID of a request that requests the container 332 to execute processing. Upon receiving the selection of the request ID by the selection unit 288, the log identification unit 287 may identify and extract log data of the OS corresponding to the selected request ID.

Output unit 290 outputs the log data identified by log identification unit 287 . Specifically, the output unit 290 may display the specified log data on an output device of the server device 200, a display device capable of communicating with the server device 200, or the like. In addition, the output unit 290 of the present embodiment can communicate with an output device that the server device 200 has a list of performance data and log data stored in the abnormal performance database 260 and the abnormal log database 270, and with the server device 200. may be displayed on a display device or the like.

Next, the processing result database 210, migration log database 220, normal state database 230, performance database 240, and log database 250 of this embodiment will be described with reference to FIGS.

FIG. 4 is a diagram explaining the processing result database. FIG. 4A shows an example of log data of the container 332 acquired by the log data acquisition unit 284. FIG. Log data 151 shown in FIG. 4A includes a time stamp 152, a request ID 153, a request destination 154, a request source 155, a processing time 156, and a response code 157. FIG.

The time stamp 152 indicates the end time of processing, and the request ID is information that uniquely identifies the request issued to the container 332 . The request destination 154 includes the name of the container 332 in which the process is executed and the called API (Application Programming Interface) 158 . The request source 155 is the name of the original container 332 that sent the request, and the processing time 156 is the time it took to complete the requested processing. The response code 157 is a three-digit code representing the meaning of the response from the server device 200 .

When log data of the container 332 is acquired, the log analysis unit 285 of this embodiment analyzes the log data and stores the log data in the processing result database 210 for each item described above.

FIG. 4B is a diagram showing an example of the processing result database 210. As shown in FIG. The processing result database 210 has time stamp, request ID, request source, request destination, API, processing time, and response code as information items. The value of each item is as described above.

In this embodiment, the log analysis unit 285 analyzes the log data of the container 332 and stores the result of associating each item with the value of the item in the processing result database 210 as processing result data.

In FIG. 4B, for example, a request specified by the request ID “550e8400” is transmitted from the container a1 to the container a2, and the API “/aaaa/bbbb” is called and executed by this request. It can be seen that the execution time is 82 [msec], the processing end time is 13:45:12 on November 11, 2018, and the response code "200" is obtained.

FIG. 5 is a diagram showing an example of a migration log database. The migration log database 220 of this embodiment includes a container position table 220-1 storing container position data in which the container 332 and the virtual machine 330 are associated with each other, and the virtual machine 330 and the information processing device (physical machine) 300. and a virtual machine location table 220-2 in which associated virtual machine location data is stored.

The container location table 220-1 includes, as information items, update time, container, and virtual machine, which are associated with each other. In FIG. 5, the container location table 220-1 shows that the container a1 and the container b1 are operating on the virtual machine Vm1.

The virtual machine location table 220-2 includes update time, virtual machine, and physical machine as information items, which are associated with each other. In FIG. 5, the virtual machine location table 220-2 shows that the virtual machine Vm1 is running on the physical machine ps1 and the virtual machine vm4 is running on the physical machine ps2.

FIG. 6 is a diagram showing an example of a normal state database. The normal state data stored in the normal state database 230 of this embodiment is generated by the normal state data generator 286 based on the processing result data stored in the processing result database 210 .

Also, the normal state data stored in the normal state database 230 is referred to when determining whether or not the state of the information processing system 100 indicated by the processing result data is normal.

The normal state database 230 of this embodiment has request source, request destination, API, upper limit of processing time, and response code as information items.

The value of the item "upper limit of processing time" is a threshold of processing time for determining whether API processing was performed normally.

For example, in the example of FIG. 6, the request source container 332 is "a1", the request destination container 332 is "a2", the API to be called is "/aaaa/bbbb", and the response code is "200 , the state indicated by the processing result data is determined to be normal if the processing time is less than 100 [msec].

FIG. 7 is a diagram illustrating an example of a performance database; The performance database 240 of this embodiment may store both the performance data of the physical machine 300 and the performance data of the virtual machine 330 .

The performance database 240 of this embodiment includes processing time, metric, value, and meta information as information items. In the following description, information including the value of each item in the performance database 240 is called performance data.

The value of the item "processing time" indicates the time when the performance data collection units 342 and 352 acquire the performance data. The value of the item "metric" indicates the type of performance, and the value of the item "value" indicates the value of performance. Specifically, for example, if the value of the item "metric" is cpu. usage and the value of the item "value" is 64.42, the type of performance is CPU usage and its value is 64.42%.

The value of the item "meta information" indicates the acquisition source of the performance data. Specifically, the value of the item "meta information" is information specifying the machine from which the performance data was acquired. For example, if the value of the item "meta information" is "ser=vm1", it can be seen that this performance data was obtained from the virtual machine vm1.

Next, the log database 250 will be described with reference to FIG. FIG. 8 is a diagram showing an example of a log database.

The log database 250 of this embodiment has processing time, processing content, meta information, etc. as information items. Log data acquired by the log data collection unit 343 and the log data collection unit 353 are stored in the log database 250 .

The value of the item "processing time" indicates the time when the log data was acquired. The value of the item "processing content" indicates the content of processing by the container management unit 334 or the hypervisor 320, the content of processing by each application operating on the container 332, the content of the operation of the OS 310, and the like. The value of the item "log data" indicates the acquisition source of the log data.

Next, the operation of the information processing system 100 of this embodiment will be described. First, the operation of the information processing apparatus 300 will be described with reference to FIGS. 9 to 13. FIG.

FIG. 9 is a flowchart for explaining the processing of the container data collecting unit of the information processing device.

In the information processing apparatus 300 of the present embodiment, the container data collection unit 351 acquires the container position data of the container 332 operating on the virtual machine 330 from the container management unit 334 at startup (step S901). (step S902).

In the server device 200 , the container data acquisition unit 281 acquires container position data and stores it in the container position table 220 - 1 of the migration log database 220 .

In other words, the container data acquisition unit 281 and the virtual machine data acquisition unit 282 of this embodiment are examples of a data acquisition unit that collects migration logs of containers.

Subsequently, the container data collection unit 351 determines whether an increase or decrease in the number of containers 332 operating on the virtual machines 330 has been detected (step S903). Specifically, the container data collection unit 351 determines whether or not a notification indicating an increase or decrease in the number of containers 332 has been received from the container management unit 334 .

If no increase or decrease is detected in step S903, the container data collection unit 351 repeats step S903.

When an increase or decrease is detected in step S903, the container data collection unit 351 acquires again the container position data of the container 332 operating on the virtual machine 330 (step S904), and transmits it to the server device 200 (step S905).

The container collection unit 351 repeats the processing shown in FIG. 9 until it receives a command to end the process. More specifically, the container data collection unit 351 repeats the processing from step S903 to step S905 in FIG. 9 until the process ends.

FIG. 10 is a flowchart for explaining processing of the virtual machine data collection unit of the information processing device.

In the information processing device 300 of this embodiment, the virtual machine data collection unit 341 acquires the virtual machine location data of the virtual machine 330 operating on the information processing device (physical machine) 300 from the hypervisor 320 at startup ( Step S1001), and transmit to the server device 200 (step S1002).

When the server device 200 acquires the virtual machine location data, the virtual machine data acquisition unit 282 stores the virtual machine location data in the virtual machine location table 220 - 2 of the migration log database 220 .

Subsequently, the virtual machine data collection unit 341 determines whether an increase or decrease in the number of virtual machines 330 operating on the information processing device 300 has been detected (step S1003). Specifically, the virtual machine data collection unit 341 determines whether or not a notification indicating an increase or decrease in the number of virtual machines 330 has been received from the hypervisor 320 .

If no increase or decrease is detected in step S1003, the virtual machine data collection unit 341 repeats step S1003.

In step S1003, when an increase or decrease is detected, the virtual machine data collection unit 341 acquires again the virtual machine position data of the virtual machine 330 operating on the information processing device 300 (step S1004), and transmits the virtual machine position data to the server device 200 (step S1004). step S1005).

The virtual machine data collection unit 341 repeats the processing shown in FIG. 10 until it receives a command instructing the end of the process. More specifically, the virtual machine data collection unit 341 repeats the processing from step S1003 to step S1005 in FIG. 10 until the process ends.

FIG. 11 is a diagram showing an example of a container position table when a decrease in containers is detected.

The container location table 220-1A in FIG. 11 shows a state in which the container data collection unit 351 has detected that the container b1 has disappeared from the virtual machine vm2. In other words, the container position table 220-1A shows the case where the container data collector 351 detects the decrease of the containers 332. FIG.

Compared to the container position table 220-1 in FIG. 5, the container position table 220-1A shown in FIG. 11 has deleted the container b1 that was running on the virtual machine Vm2.

FIG. 12 is a diagram illustrating an example of a virtual machine location table when an increase in virtual machines is detected.

The virtual machine location table 220-2A in FIG. 12 shows a state in which the virtual machine data collector 341 has detected that the virtual machine vm1 has been added to the physical machine ps2. In other words, the virtual machine location table 220-2A indicates the case where the virtual machine data collector 341 detects an increase in the number of virtual machines.

Virtual machine location table 220-2A shown in FIG. 12 has virtual machine Vm1 running on physical machine ps2 added, compared to virtual machine location table 220-2 of FIG.

In this way, the server device 200 of the present embodiment associates information in which containers and virtual machines on which the containers operate are associated in time series with virtual machines and physical machines on which the virtual machines operate in time series. The attached information is held in the migration log database 220 . In other words, it can be said that the migration log database 220 of this embodiment stores a migration log indicating a history of movement of containers.

FIG. 13 is a flowchart for explaining the processing of the performance data collection unit. In the information processing device 300 of this embodiment, the performance data collection unit 342 periodically acquires performance data of the information processing device 300 and the OS 310, and the performance data collection unit 352 collects performance data of the virtual machine 330 and the container 332. Acquire (step S1301).

Subsequently, the performance data collection unit 342 and the performance data collection unit 352 transmit the performance data they have acquired to the server device 200 (step S1302).

The performance data collection unit 342 and the performance data collection unit 352 repeat the processing shown in FIG. 13 until receiving a command instructing the end of each process.

In the information processing apparatus 300 , the log data collection unit 343 and the log data collection unit 353 also periodically collect log data in the same manner as the performance data collection unit 342 and the performance data collection unit 352 and send the log data to the server device 200 . sending.

Next, referring to FIG. 14, the operation of the server device 200 of this embodiment will be described. FIG. 14 is a flowchart for explaining the processing of the log reference processing unit of the server device.

The log reference processing unit 280 of the server device 200 of the present embodiment collects log data of processing performed on the container 332 from the container data collection unit 351 of the information processing device 300 by the container data acquisition unit 281 (step S1401).

Subsequently, the log reference processing unit 280 analyzes the log data collected from the container 332 by the log analysis unit 285, converts the log data into processing result data indicating the processing content, processing time, and processing result, and stores the data in the processing result database 210. , the log data of the container 332 and the log data other than the container 332 are stored in the log database 250 (step S1402).

Specifically, the log reference processing unit 280 acquires the log data of the OS 310 from the log data collection unit 343 using the log data acquisition unit 284, and the log data of the OS 331 and the log data of the virtual machine 330 Data is acquired and stored in the log database 250 .

Subsequently, the log reference processing unit 280 determines whether normal state data has been generated in the normal state database 230 by the normal state data generating unit 286 (step S1403).

In step S1403, if the normal state data has already been generated, the log reference processing unit 280 proceeds to step S1406, which will be described later.

In step S1403, if the normal state data has not been generated, the log reference processing unit 280 determines whether or not the number of records of the processing result data stored in the processing result database 210 is equal to or greater than a predetermined number (step S1404). . In step S1404, if the number of records is less than the predetermined number, log reference processing section 280 returns to step S1401.

In step S1404, if the number of records is equal to or greater than the predetermined number, the normal state data generation unit 286 generates normal state data, stores it in the normal state database 230 (step S1405), and returns to step S1401.

Specifically, the normal state data generation unit 286 of this embodiment determines a specific condition based on the processing result data stored in the processing result database 210, and uses data indicating this condition as normal state data. Store in state database 230 .

Specific conditions include, for example, that the processing time included in the processing result data is less than the upper limit of the processing time, that the response code is a response code with a frequency of appearance equal to or greater than a predetermined value, and the like. These specific conditions are conditions that can be set from the outside by, for example, an administrator of the information processing system 100 or the like.

In step S1403, if the normal state data has already been generated, the log reference processing unit 280 determines whether or not a certain period of time has passed since the normal state database 230 was updated (step S1406). In step S1406, if the predetermined time has not elapsed, the log reference processing unit 280 proceeds to step S1404.

In step S1406, if the predetermined time has not elapsed, the log reference processing unit 280 causes the log analysis unit 285 to compare the processing result data with the normal state data stored in the normal state database 230 (step S1407).

Subsequently, the log analysis unit 285 determines whether or not the process indicated by the process result data was normally processed (step S1408). In step S1408, if the process is normal, the log reference processing unit 280 returns to step S1401.

In step S1408, if the processing is not normal, that is, if it is determined that the state is abnormal, the log reference processing unit 280 causes the selection unit 288 to select the request ID included in the processing result data, and specify the log. The unit 287 extracts processing result data including the same request ID as the selected request ID in the processing result database 210 (step S1409).

Subsequently, the log identifying unit 287 identifies and extracts the log data and performance data of the container 332 included in the process result data extracted from the log database 250 and performance database 240 (step S1410). The containers 332 included in the processing result data are the container 332 corresponding to the request destination of the processing result data and the container 332 corresponding to the request source.

Subsequently, the log specifying unit 287 extracts the time stamp of the first acquired processing result data and the time stamp of the last acquired processing result data from among the processing result data extracted in step S1409 ( step S1411).

Subsequently, the log identification unit 287 refers to the migration log database 220, and associates the container 332, the virtual machine 330, and the information processing device (physical machine) 300 with the processing time calculated from the extracted time stamp. A list to be displayed is created (step S1412).

Subsequently, the log identifying unit 287 acquires performance data and log data for the processing time calculated from the time stamp for the virtual machine 330 and the information processing device 300 included in the list (step S1413). The log data acquired here includes log data of the OS 331 of the virtual machine 330 and log data of the OS 310 of the information processing device (physical machine) 300 .

In other words, the log identification unit 287 of this embodiment selects a request ID that is part of the execution log data of the process in the container, refers to the migration log database 220, and refers to the container that executed the process indicated by the selected request ID. , and based on the location of the container, extract the log data of the OS related to the container.

Subsequently, the log identifying unit 287 assigns a request ID to the meta information of the performance data and log data acquired in step S1413, and stores them in the abnormal performance database 260 and the abnormal log database 270 (step S1414). , terminate the process. At this time, the log specifying unit 287 also stores the log data of the container 332 acquired in step S1410 in the error log database 270. FIG.

The processing in FIG. 14 will be specifically described below with reference to FIGS. 15 to 17. FIG. FIG. 15 is a diagram for explaining comparison between processing result data and normal state data. Specifically, FIG. 15 is a diagram for explaining the process of step S1408 in FIG.

15A shows the normal state database 230, and FIG. 15B shows the processing result database 210. FIG.

In the example of FIG. 15, the processing result data 210-1 stored in the processing result database 210 has a request ID of "550e8400", a request source container 332 of "a1", and a request destination container 332 of " a2", the API to be called is "/aaaa/bbbb", the response code is "200", and the processing time is 82 [msec].

On the other hand, in the normal state data 230-1 of the normal state database 230, the request source container 332 is "a1", the request destination container 332 is "a2", and the API to be called is "/aaaa/bbbb ” and the response code is “200”, the upper limit of the processing time is 100 [msec].

Therefore, the log analysis unit 285 determines that the processing indicated by the request ID "550e8400" in the processing result data 210-1 was normally processed, and proceeds to step S1401 in FIG.

In the processing result data 210-2 stored in the processing result database 210, the request ID is "550e8400", the request source container 332 is "a4", and the request destination container 332 is "a3". , the API to be called is "/aaaa/bbbb", the response code is "200", and the processing time is 103 [msec].

On the other hand, in the normal state data 230-2 of the normal state database 230, the request source container 332 is "a4", the request destination container 332 is "a3", and the API to be called is "/aaaa/bbbb ” and the response code is “200”, the upper limit of the processing time is 100 [msec].

Therefore, log analysis unit 285 determines that processing result data 210-2 exceeds the upper limit of processing time and is not processed normally, and proceeds to step S1409 in FIG.

FIG. 16 is a diagram showing an example of intermediate data. Specifically, FIG. 16 is a diagram for explaining the processing from step S1409 to step S1412 in FIG.

FIG. 16A shows an example of the result of extracting the processing result data whose request ID matches the processing result data determined to have not been processed normally.

In FIG. 15, it is determined that the processing result data 210-2 has not been processed normally. Therefore, the log specifying unit 287 extracts the processing result data including the request ID “550e8400” included in the processing result data 210 - 2 and generates the intermediate data 171 .

The intermediate data 171 includes a times end, a container, and a processing time. Here, the log specifying unit 287 extracts the processing result data 210-1, 210-2, 210-3 including the request ID "550e8400" from the processing result database 210 shown in FIG.

Then, the log identification unit 287 creates intermediate data in which the container corresponding to the “request destination” indicating the container that executed the processing identified by the request ID, the time stamp indicating the completion time of the processing, and the processing time are associated with each other. 171.

From this intermediate data 171, it can be seen that the processing specified by the request ID "550e8400" was executed by the containers a2, a4, and a3.

In the intermediate data 171, the time stamp of the processing result data obtained first is the time stamp of the processing result data 210-1, and the time stamp of the processing result data obtained last is the time stamp of the processing result data 210-2. is the timestamp of

Therefore, the start time of the process specified by the request ID "550e8400" is the time 82 [msec] before the time indicated by the time stamp of the process result data 210-1, which is the processing time of the process result data 210-1. be. Also, the end time of the process specified by the request ID "550e8400" is the time indicated by the time stamp of the process result data 210-2.

The log specifying unit 287 calculates the processing time required for the process specified by the request ID "550e8400" from the start time and end time of the process specified by the request ID "550e8400".

Then, the log identification unit 287 refers to the migration log database 220 and generates intermediate data 172 showing a list of associations between the containers 332, the virtual machines 330, and the information processing devices 300 in the time period indicated by the calculated processing time. do.

In the intermediate data 172 shown in FIG. 16B, the container a2 and the container a4 operate on the virtual machine vm1, and the container a3 operates on the virtual machine vm4 during the processing time specified by the request ID "550e8400". I know you are. Also, it can be seen that the virtual machine vm1 operates on the physical machine ps1, and the virtual machine vm4 operates on the physical machine ps2.

The log identification unit 287 of this embodiment obtains performance data and logs during the processing time of the processing identified by the request ID "550e8400" for the virtual machines vm1 and vm4 and the physical machines ps1 and ps2 included in the intermediate data 172. Data is extracted from performance database 240 and log database 250 .

Then, the log specifying unit 287 assigns the request ID “550e8400” to the extracted meta information of the performance data and log data. Then, the log identifying unit 287 stores the performance data with the request ID added to the meta information in the abnormal performance database 260, and stores the log data with the request ID added to the meta information in the abnormal log database 270. .

FIG. 17 is a diagram illustrating an example of an abnormal performance database. In the abnormal performance database 260 shown in FIG. 17, the request ID "550e8400" is assigned to the value of the item "meta information".

In this embodiment, every time the correspondence between the container and the virtual machine and the correspondence between the virtual machine and the physical machine are changed, data indicating these correspondences are generated and generated. It is stored in the migration log database 220 in association with the time.

In addition, in this embodiment, when a process uniquely identified by a request ID is not executed normally, the container that executed the process identified by the request ID and the virtual machine on which the container was running during the processing time and the physical machine on which the virtual machine was running.

Then, in this embodiment, the performance data and log data during the processing time of the specified virtual machine and physical machine are extracted, the request ID is given to the meta information, and the data is sent to the abnormal performance database 260 and the abnormal log database 270. Store.

The abnormal performance database 260 and the abnormal log database 270 are provided in storage areas different from the performance database 240 and the log database 250 . Also, compared to the performance database 240 and the log database 250, the period of data retention is set to be longer.

In this embodiment, as described above, information identifying a process that has not been executed normally, and performance data and logs of the container that was executing this process and the corresponding virtual machine and physical machine during execution of this process. It is stored in association with data.

Therefore, according to this embodiment, by selecting a request ID, it is possible to specify the position of the container that executed the process specified by this request ID and the log data of the OS 310 and OS 331 related to the container. .

Therefore, according to the present embodiment, for example, when a failure occurs in a container, it is possible to specify the log data to be referenced related to this container.

FIG. 18 is a diagram showing a display example of log data. FIG. 18 shows an output example (display example) of information stored in the abnormal performance database 260 and the abnormal log database 270 .

The screen 181 shown in FIG. 18 may be displayed, for example, on the display (output device) of the server device 200, or may be displayed on a terminal of the administrator of the information processing system 100 and capable of communicating with the server device 200. May be displayed.

The screen 181 has a display column 183 and a display column 184 . The display column 183 displays information indicating the correspondence between the container 332 , the virtual machine 330 and the physical machine 300 . The display field 184 displays the log data and performance data of the selected container 332, virtual machine 330, and physical machine 300 displayed in the display field 183, according to the selection.

Further, in this embodiment, for example, a selection column for selecting a request may be displayed on the screen 181 . Then, when the request ID is selected in the selection, the log reference processing unit 280 receives this selection by the selection unit 288, and specifies the log data of the OS corresponding to the selected request ID by the log specifying unit 287. , may be displayed in the display field 184 by the output unit 290 .

In this embodiment, the migration log database 220 is referred to, and the log data of the OS related to the container is extracted from part of the execution log data of the processing by the container. However, the present invention is not limited to this.

The log identification unit 287 of the present embodiment, for example, identifies the container from the log data of the OS stored in the log database 250 and the abnormal log database 270, and the performance data stored in the performance database 240 and the abnormal performance database 260. You can also extract execution log data.

The procedure will be described below.

The log identifying unit 287 of the present embodiment receives selection of OS log data stored in the abnormal log database 270 when, for example, a problem occurs in the OS 310 or 331 . The selection of OS log data may be, for example, the result of comparison with normal state data indicating the normal state of the OS 310 or OS 331, or may be selected by an administrator of the information processing system 100 or the like. .

Next, when the selected log data is the OS 310 of the information processing device 300, the log identification unit 287 identifies the processing time of the log data and the virtual machine 330 included in the meta information. Next, the log identification unit 287 refers to the migration log database 220 and identifies the container 332 operating on the identified virtual machine 330 at the identified processing time. Then, the log identification unit 287 extracts execution log data of the process executed by the identified container 332 at the identified processing time from the log database 250 .

Further, when the selected log data is the OS 331 of the virtual machine 330, the log identification unit 287 identifies the processing time of the log data and the container 332 included in the meta information. Then, the log identification unit 287 extracts execution log data of the process executed by the identified container 332 at the identified processing time from the log database 250 .

As described above, in the present embodiment, by referring to the migration log indicating the history of migration of containers between virtual machines and the history of migration of virtual machines between physical machines, it is possible to obtain information about the relationship between containers from log data of containers. It is possible to specify and extract the log data of the operating system. Further, in this embodiment, it is possible to identify and extract log data of a container that was operating during the time period indicated by the log data from the log data of the OS.

The technology disclosed herein can take forms such as those described below.
(Appendix 1)
a data acquisition unit that collects container migration logs;
a log identifying unit that refers to the migration log and identifies log data of an operating system related to the container and the location of the container when a portion of the execution log of the container is selected. Information processing equipment.
(Appendix 2)
The migration log is
container location data including a correspondence between the container and the virtual machine on which the container was running, and a time at which the container and the virtual machine were associated;
virtual machine location data including an association between the virtual machine and the physical machine on which the virtual machine was running, and a time at which the virtual machine and the physical machine were associated 1. The information processing device according to 1.
(Appendix 3)
the container location data is obtained each time the virtual machine on which the container runs is changed;
The information processing apparatus according to appendix 2, wherein the virtual machine location data is acquired each time a physical machine on which the virtual machine operates is changed.
(Appendix 4)
The log identification unit
4. The information processing apparatus according to any one of appendices 1 to 3, wherein a request ID that is a part of the execution log of the container is added to the specified log data and stored in a storage unit.
(Appendix 5)
The log identification unit
When the log data of the operating system is selected, the migration log is referred to, and based on the meta information included in the log data of the operating system, an operation is performed when the selected log data of the operating system is acquired. 5. The information processing apparatus according to any one of appendices 1 to 4, wherein the execution log data of a container that has been running is identified and extracted.
(Appendix 6)
The log data of the operating system is
6. Any one of Appendices 1 to 5, including log data of an operating system running on a virtual machine corresponding to the container, and log data of an operating system running on a physical machine on which the virtual machine runs. The information processing device according to the item.
(Appendix 7)
a normal state data generation unit that generates normal state data that is referred to in determining whether or not the processing by the container has been executed normally, based on the execution log data of the container;
a log analysis unit that compares the execution log data and the normal state data to determine whether the processing by the container has been executed normally,
The log identification unit
7. The information processing according to any one of appendices 1 to 6, wherein log data of an operating system related to the container and the location of the container are specified when the processing by the container is not executed normally. Device.
(Appendix 8)
8. The information processing apparatus according to any one of appendices 1 to 7, further comprising an output unit that associates and displays the log data identified by the log identification unit and the position of the container.
(Appendix 9)
Collect the migration log of the container,
When a portion of the execution log of the container is selected, causing a computer to perform a process of referring to the migration log and identifying log data of an operating system related to the container and the location of the container. Log reference program.

100 information processing system 200 server device 210 processing result database 220 migration log database 230 normal state database 240 performance database 250 log database 260 failure time performance database 270 failure time log database 280 log reference processing unit 281 container data acquisition unit 282 virtual machine data acquisition Unit 283 Performance data acquisition unit 284 Log data acquisition unit 285 Log analysis unit 286 Normal state data generation unit 287 Log identification unit 300 Information processing device (physical machine)
310, 331 OS
320 hypervisor 330 virtual machine 332 container 333 proxy 334 container management unit 341 virtual machine data collection unit 342, 352 performance data collection unit 343, 353 log data collection unit 351 container data collection unit

Claims (6)

a data acquisition unit that collects a migration log indicating a history of container movement ;
a log identifying unit that refers to the migration log and identifies log data of an operating system related to the container and the location of the container when a portion of the execution log of the container is selected. Information processing equipment. The migration log is
container location data including a correspondence between the container and the virtual machine on which the container was running, and a time at which the container and the virtual machine were associated;
virtual machine location data including an association between the virtual machine and the physical machine on which the virtual machine was running, and a time at which the virtual machine and the physical machine were associated Item 1. The information processing apparatus according to item 1. the container location data is obtained each time the virtual machine on which the container runs is changed;
3. The information processing apparatus according to claim 2, wherein said virtual machine location data is obtained each time a physical machine on which said virtual machine operates is changed. The log identification unit
4. The information processing apparatus according to any one of claims 1 to 3, wherein a request ID that is part of the execution log of said container is added to said specified log data and stored in a storage unit. The log identification unit
When the log data of the operating system is selected, the migration log is referred to, and based on the meta information included in the log data of the operating system, an operation is performed when the selected log data of the operating system is acquired. 5. The information processing apparatus according to any one of claims 1 to 4, wherein execution log data of a container that has been running is specified and extracted. Collect a migration log that shows the history of container movement ,
When a portion of the execution log of the container is selected, causing a computer to perform a process of referring to the migration log and identifying log data of an operating system related to the container and the location of the container. Log reference program.

Images