Log management device, log management method, and log management program

The log management device optimizes storage for microservice observation information by identifying request IDs, searching for errors and warnings, and adjusting storage accordingly, ensuring efficient database use and cost-effectiveness.

JP2024168360AInactive Publication Date: 2024-12-05FUJITSU LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023084935
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-23
Publication Date
2024-12-05
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Conventional technologies fail to adjust the amount of storage for observation information about microservices, leading to inefficient use of database resources due to high or low density of data, which can result in either overwhelming the database or insufficient data for system evaluation.

Method used

A log management device and method that identifies a series of operations using a request ID, searches for error and warning information, and adjusts storage based on the presence of these indicators, storing only relevant information in a database to optimize storage capacity.

Benefits of technology

This approach allows for efficient storage management by reducing the amount of data stored while maintaining sufficient information for system performance evaluation, thereby optimizing database usage and reducing costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024168360000001_ABST
    Figure 2024168360000001_ABST
Patent Text Reader

Abstract

To make it possible to adjust the amount of observation information regarding microservices to be stored in a database that serves as a storage location of the observation information.SOLUTION: A log management device 101 is configured to obtain observation information group (for example, observation information groups 121-123) including the same request ID, in observation information (for example, observation information set 120) collected from each microservice of a plurality of the microservices. The observation information is information on processes executed on the microservices. The request ID is an identifier for identifying a series of processes to be executed in response to a request. A log management device 101 searches the obtained observation information group for error information and warning information. The error information is information indicating occurrence of an error. The warning information is information indicating occurrence of an event that may cause an error. The log management device 101 stores, in a database 110, some or all of the pieces of information of the observation information group depending on a search result of the search.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a log management device, a log management method, and a log management program. [Background technology]

[0002] A microservice is a software structure that configures a single service by combining multiple software components that are developed and run independently. In order to monitor the operation status of a microservice application program, observation information of the microservice may be collected. The observation information of the microservice may be collected, for example, without stopping the operation of the system, and used to evaluate the performance of the system.

[0003] Prior art includes a monitoring system in which an agent device sequentially acquires monitoring values ​​from a processing unit, removes noise from the monitoring values ​​to generate removed monitoring values, and transmits the removed monitoring values ​​to a manager device, and the manager device determines a monitoring interval for acquiring monitoring values ​​from the agent device by referring to the removed monitoring values ​​acquired from the agent device. There is also a technology for managing notifications regarding the execution of microservices. There is also a technology for managing multiple business devices that periodically distribute data using telemetry technology. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2021 / 095114 [Patent Document 2] US Patent Application Publication No. 2022 / 0245017 [Patent Document 3] JP 2020-28005 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the conventional technology has a problem in that it is not possible to adjust the amount of data stored in a database that stores observation information about microservices that is collected for purposes such as evaluating system performance.

[0006] In one aspect, the present invention aims to make it possible to adjust the amount of storage in a database in which observation information about microservices is stored. [Means for solving the problem]

[0007] In one embodiment, a log management device is provided that acquires a group of observation information including an identical request ID that identifies a series of processes executed in response to a request from observation information collected from each microservice of a plurality of microservices, searches the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of an error, and stores some or all of the information from the group of observation information in a database as a storage destination depending on the search results. Effect of the Invention

[0008] Advantageous Effects of Invention One aspect of the present invention has the effect of making it possible to adjust the amount of storage in a database in which observation information about a microservice is stored. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of a log management method according to an embodiment. [Diagram 2] FIG. 2 is an explanatory diagram showing an example of a system configuration of an information processing system 200. As shown in FIG. [Diagram 3] FIG. 3 is a block diagram showing an example of the hardware configuration of the log management server 201. As shown in FIG. [Figure 4] FIG. 4 is a block diagram showing an example of the functional configuration of the log management server 201. As shown in FIG. [Diagram 5]FIG. 5 is an explanatory diagram showing an example of the operation of the information processing system 200. As shown in FIG. [Figure 6] FIG. 6 is an explanatory diagram showing a first operation example of an application. [Figure 7A] FIG. 7A is an explanatory diagram (part 1) showing a first example sample of telemetry data. [Figure 7B] FIG. 7B is an explanatory diagram (part 2) showing a first sample example of telemetry data. [Figure 7C] FIG. 7C is an explanatory diagram (part 3) showing a first example sample of telemetry data. [Figure 7D] FIG. 7D is an explanatory diagram (part 4) showing a first example sample of telemetry data. [Figure 7E] FIG. 7E is an explanatory diagram (part 5) showing a first example sample of telemetry data. [Figure 7F] FIG. 7F is an explanatory diagram (part 6) showing a first example sample of telemetry data. [Figure 8A] FIG. 8A is an explanatory diagram (part 1) showing a first creation example of a formatted log. [Figure 8B] FIG. 8B is an explanatory diagram (part 2) showing a first creation example of the formatted log. [Figure 9] FIG. 9 is an explanatory diagram showing a first storage example of the structured log. [Figure 10A] FIG. 10A is an explanatory diagram (part 1) showing a second creation example of the formatted log. [Figure 10B] FIG. 10B is an explanatory diagram (part 2) showing a second example of creating a formatted log. [Figure 11] FIG. 11 is an explanatory diagram showing a second example of storage of the structured log. [Figure 12] FIG. 12 is an explanatory diagram showing a second operation example of the application. [Figure 13A] FIG. 13A is an explanatory diagram (part 1) showing a second sample example of telemetry data. [Figure 13B]FIG. 13B is an explanatory diagram (part 2) showing a second sample example of the telemetry data. [Figure 13C] FIG. 13C is an explanatory diagram (part 3) showing a second example sample of the telemetry data. [Figure 14A] FIG. 14A is an explanatory diagram (part 1) showing a second creation example of the formatted log. [Figure 14B] FIG. 14B is an explanatory diagram (part 2) showing a second example of creating a formatted log. [Figure 15] FIG. 15 is an explanatory diagram showing a third storage example of the structured log. [Figure 16] FIG. 16 is an explanatory diagram showing a third operation example of the application. [Figure 17A] FIG. 17A is an explanatory diagram (part 1) showing a second sample example of telemetry data. [Figure 17B] FIG. 17B is an explanatory diagram (part 2) showing a second example sample of the telemetry data. [Figure 17C] FIG. 17C is an explanatory diagram (part 3) showing a second example sample of telemetry data. [Figure 18A] FIG. 18A is an explanatory diagram (part 1) showing a second creation example of the formatted log. [Figure 18B] FIG. 18B is an explanatory diagram (part 2) showing a second example of creating a formatted log. [Figure 19] FIG. 19 is an explanatory diagram showing a fourth storage example of the structured log. [Figure 20] FIG. 20 is a flowchart (part 1) illustrating an example of a log management process procedure of the log management server 201. [Figure 21] FIG. 21 is a flowchart (part 2) illustrating an example of the log management processing procedure of the log management server 201. [Figure 22] FIG. 22 is a flowchart (part 1) illustrating an example of a specific processing procedure of the formatting process. [Diagram 23] FIG. 23 is a second flowchart illustrating an example of a specific procedure of the formatting process. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of a log management device, a log management method, and a log management program according to the present invention will be described in detail with reference to the accompanying drawings.

[0011] (Embodiment) Fig. 1 is an explanatory diagram showing an example of a log management method according to an embodiment. In Fig. 1, a log management device 101 is a computer that adjusts the amount of data stored in a database 110 that is a storage destination for observed information collected from each microservice of a plurality of microservices. A microservice is an architecture in which one service is divided into functions, or software that realizes each of the divided functions of one service.

[0012] By making a system into microservices, functions can be added or faults fixed by simply replacing individual microservices, which is expected to improve the speed of correction and availability without stopping the entire system. Each microservice is executed by a different server, for example. The server is, for example, a physical server or a virtual machine. Microservices may also be executed by containers.

[0013] The multiple microservices include, for example, microservices that have a call relationship. The multiple microservices that have a call relationship are a collection of microservices that realize a system, and the microservices included in the multiple microservices realize their functions by calling other microservices.

[0014] Observation information is information about processes executed in a microservice, and is used to observe the behavior of the microservice. Observation information is also called log information. There are multiple data types of observation information. Examples of data types include events, metrics, logs, and traces.

[0015] An event is a record of an individual request or action that occurred at a certain time. Metrics are measured, aggregated, or other numerical information about the execution of a microservice. Logs are information (text data) generated by the system when individual operations are performed within an application or platform.

[0016] A trace is information that indicates the order in which services are called when a request is processed across multiple services. Error and warning messages may be output together with numerical metrics information or output as logs.

[0017] A system (service) consisting of multiple microservices is a distributed service system for each microservice. For this reason, it is important to properly manage each microservice and monitor them to ensure that they operate efficiently. Also, incorporating logic for monitoring the status of a microservice into each microservice would require preparing metrics and libraries for each distributed microservice, which is inefficient.

[0018] For this reason, there are cases where observation information is collected to monitor the operating status of each microservice (application program) and to evaluate the system performance, etc. On the other hand, the microservice architecture deployed in the cloud is configured to be scalable by using multiple microservices.

[0019] As the microservice architecture expands, the amount of observational data collected from the microservices increases, leading to an increase in the memory space required to store the data. In addition, in order to secure the memory space required to store data in the cloud, charges are often required according to the amount of data collected and the amount of data transferred.

[0020] Conventionally, in a system consisting of multiple microservices, there is a mechanism called "service mesh" that properly manages communication between services connected in a mesh to prevent management of distributed microservices from collapsing. In a service mesh, a lightweight proxy is set up for each microservice to realize management functions such as service discovery, traffic control, observability, fault isolation, and security.

[0021] Service discovery is a mechanism for identifying the location of the microservice to be called on the network. Traffic control is a mechanism for controlling communication between services by changing the allocation of access to a microservice based on settings or by changing the return value from the microservice.

[0022] Observability is a mechanism for checking the internal state from the data output by a microservice and judging the normality of the microservice. Fault isolation is a mechanism for minimizing the scope of impact when a failure occurs in an individual microservice. Security is a mechanism for efficiently managing authentication / authorization and secure communication when a microservice calls other microservices.

[0023] Here, the service mesh includes, for example, two components: a control plane and a data plane. The control plane is responsible for managing the service mesh, storing information necessary for management such as service discovery, and issuing management commands such as configuration changes. The data plane receives instructions from the control plane to control service communications and transmits information necessary for management to the control plane.

[0024] For example, the control plane can collect the observation information of each microservice from the data plane using the observability mechanism of the service mesh. The control plane, for example, stores the observation information collected from each data plane in a database and performs system performance evaluation (improvement of the system or application, identification of fault locations, etc.).

[0025] However, conventional technologies cannot adjust the amount of observation information collected about microservices stored in a database. For example, the amount of collected observation information can become huge under various conditions if the data is highly dense (many types of data, short collection interval), putting strain on the database and storage.

[0026] On the other hand, if the density is low (few data types, long aggregation intervals) to avoid straining the database and storage, data shortages will occur when a failure occurs or when improvements are made to the system or application. With conventional technology, it is not possible to determine what criteria should be used to adjust the amount of observation information stored in the database.

[0027] In this embodiment, therefore, a log management method that makes it possible to adjust the amount of data stored in a database (for example, database 110) that stores observation information about a microservice will be described. Here, examples of processing by the log management device 101 (corresponding to the following processing (1) to (3)) will be described.

[0028] (1) The log management device 101 acquires a group of observation information including the same request ID from among the observation information collected from each microservice of a plurality of microservices. The observation information is information about the processing executed in each microservice. The request ID is an identifier that identifies a series of processing executed in response to a request.

[0029] The observation information includes a request ID to identify the chain of requests across microservices. By continuing to use this request ID throughout a series of processes, it becomes possible to extract observation information related to a series of processes from the vast number of observation information collected.

[0030] 1, the observation information set 120 is a set of observation information collected from each microservice of a plurality of microservices. In this case, the log management device 101 acquires an observation information group including the same request ID from the observation information set 120. Here, it is assumed that observation information sets 121 to 123 including the same request ID ("ID" in FIG. 1) have been acquired.

[0031] (2) The log management device 101 searches for error information and warning information from the acquired observation information group. Here, error information is information indicating the occurrence of an error. Warning information is information indicating the occurrence of an event that may be the cause of an error. Events that may be the cause of an error include, for example, "long processing time," "slow response," and "absence of certain information."

[0032] Error information and warning information may be included in the observation information. Error information in the observation information is identified by a character string such as "ERROR" or "error". Warning information in the observation information is identified by a character string such as "WARN" or "warning".

[0033] (3) The log management device 101 stores some or all of the information in the observation information group in the database 110 according to the search results. The database 110 is a database in which the observation information is stored. The database 110 may be owned by the log management device 101, or may be owned by another computer accessible from the log management device 101.

[0034] If no error or warning information is found in the observation information group, the system is operating normally and a series of processes is completed, and there is little need to store the entire observation information group. For this reason, the log management device 101 reduces the amount of data stored in the database 110 by, for example, storing only a predetermined portion of the observation information group.

[0035] The part of the information may include, for example, information (event) of the process that is the starting point of the operation according to the request, or a request ID. The part of the information may also include information indicating the transition of the microservice that operated according to the request. The part of the information may also include metrics information and a status code when the operation according to the request ends.

[0036] If no error information is found in the observation information group, but warning information is found, this is a case where no error occurred during the series of processes, but an event that could have caused an error occurred. In this case, the event should be analyzed to determine whether further investigation is necessary.

[0037] For this reason, the log management device 101 may store, for example, only observation information of the same data type as the observation information including warning information from the group of observation information in the database 110. Observation information of the same data type as the observation information including warning information can be said to be useful information for analyzing events that may be the cause of errors.

[0038] Furthermore, the log management device 101 may store only the observation information including warning information from the observation information group in the database 110. This reduces the amount of data stored in the database 110 compared to when the log management device 101 stores the entire observation information group. However, the log management device 101 may store the entire observation information group in the database 110 when warning information is found.

[0039] Also, when error information is found from the observation information group, it means that some kind of error has occurred during the series of processes, and it is necessary to identify the location of the failure and the cause and take appropriate action. For this reason, the log management device 101 stores, for example, all of the observation information group in the database 110.

[0040] 1, it is first assumed that no error information or warning information is found from the observation information groups 121 to 123. In this case, the log management device 101 extracts, for example, a predetermined portion of information 130 from the observation information groups 121 to 123. Then, the log management device 101 may store in the database 110 only the extracted portion of information 130 for the observation information groups 121 to 123.

[0041] Also, assume that no error information is found and warning information is found from observation information groups 121-123. In this case, log management device 101 extracts, for example, observation information including warning information from observation information groups 121-123. Here, assume that observation information 121 and 122 including warning information are extracted. In this case, log management device 101 may store the extracted observation information 121 and 122 for observation information groups 121-123 in database 110. At this time, log management device 101 may store the extracted observation information 121 and 122 in database 110 together with some information 130.

[0042] Also, assume that error information is searched for from observation information groups 121 to 123. In this case, log management device 101 may, for example, store observation information groups 121 to 123 in database 110. At this time, log management device 101 may store observation information groups 121 to 123 in database 110 together with some information 130.

[0043] In this way, the log management device 101 can adjust the amount of storage in the database 110, which is the storage destination of observation information about a microservice. For example, the log management device 101 can adjust whether to store only a portion of the observation information group or all of the information, depending on whether error information or warning information is included, for each observation information group linked to the same request ID. As a result, the log management device 101 can reduce the storage capacity used to store observation information in the database 110, while retaining information useful for system performance evaluation and the like.

[0044] (System configuration example of information processing system 200) Next, a system configuration example of an information processing system 200 including the log management device 101 shown in Fig. 1 will be described. Here, a case where the log management device 101 shown in Fig. 1 is applied to a log management server 201 in the information processing system 200 will be described as an example. The information processing system 200 is applied to a computer system that provides web services by utilizing a microservice architecture, for example.

[0045] Fig. 2 is an explanatory diagram showing an example of a system configuration of an information processing system 200. In Fig. 2, the information processing system 200 includes a log management server 201 and processing devices M1 to Mm (m: a natural number equal to or greater than 2). In the information processing system 200, the log management server 201 and the processing devices M1 to Mm are connected via a wired or wireless network 210. The network 210 is, for example, the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network).

[0046] Here, the log management server 201 is a computer that adjusts the amount of telemetry data stored in the database 220. The database 220 is a database that stores the telemetry data. The telemetry data corresponds to observation information output from each microservice of a plurality of microservices.

[0047] The database 220 includes database Lv1, database Lv2, and database Lv3. The databases Lv1, Lv2, and Lv3 correspond to different storage areas (first storage area, second storage area, and third storage area) divided within the database 220. The database 110 illustrated in FIG. 1 corresponds to the database 220, for example.

[0048] Here, a case will be described in which the log management server 201 has the database 220. However, the database 220 may be included in another computer (for example, a database server) accessible from the log management server 201.

[0049] The log management server 201 also has a control plane C. The control plane C is one of the components that make up the service mesh, and is responsible for managing the service mesh. The control plane C stores information necessary for managing the microservices connected by the service mesh, and issues management commands such as configuration changes. For example, the control plane C controls communication related to the service by sending management instructions to the data plane, thereby managing the microservices.

[0050] The processing devices M1 to Mm are computers capable of executing each of a plurality of microservices. A microservice is a software component that operates independently. A single service (application, system) is configured by interconnecting and combining a plurality of software components.

[0051] Specifically, for example, each of the processing devices M1 to Mm may start a container on its own device and execute a microservice on the container. The processing devices M1 to Mm may be, for example, a physical server or a virtual machine operating on a physical server.

[0052] The processing devices M1 to Mm can also execute a data plane. The data plane is one of the components that make up the service mesh, and receives instructions from the control plane C to control communication of microservices and transmits information required for management to the control plane.

[0053] In the following description, any of the processing devices M1 to Mm may be referred to as the "processing device Mi" (i = 1, 2, ..., m). A microservice executed on the processing device Mi may be referred to as the "service #i". A data plane operating on the processing device Mi may be referred to as the "data plane #i". For example, a microservice executed on the processing device M1 is "service #1", and a data plane operating on the processing device M1 is "data plane #1". A microservice executed on the processing device Mm is "service #m", and a data plane operating on the processing device Mm is "data plane #m".

[0054] In the information processing system 200, the data plane #i acquires telemetry data related to the service #i. At this time, the data plane #i assigns a request ID that identifies a series of processes executed in response to the request to the telemetry data. Then, the data plane #i transmits the acquired telemetry data (including the request ID) to the control plane C.

[0055] The transmission of telemetry data by the data plane #i is performed periodically, for example, at predetermined time intervals. For example, the data plane #i acquires telemetry data in response to the execution of the service #i. Then, each time a certain period of time has elapsed, the data plane #i collectively transmits the telemetry data acquired during that period to the control plane C. However, the data plane #i may transmit the acquired telemetry data to the control plane C each time it acquires telemetry data related to the service #i.

[0056] Although not shown in the figure, the information processing system 200 includes a user terminal used by a user of the information processing system 200. The user terminal is, for example, a PC (Personal Computer) or a tablet PC. The information processing system 200 may also include a database, a camera, a robot, a sensor, and the like that are accessed by the service 3i. For example, the service 3i accesses a database to read and write data, and accesses a sensor to obtain sensor data.

[0057] (Example of hardware configuration of log management server 201) Next, an example of the hardware configuration of the log management server 201 will be described.

[0058] Fig. 3 is a block diagram showing an example of the hardware configuration of the log management server 201. In Fig. 3, the log management server 201 has a CPU (Central Processing Unit) 301, a memory 302, a disk drive 303, a disk 304, a communication I / F (Interface) 305, a portable recording medium I / F 306, and a portable recording medium 307. Furthermore, each component is connected to each other via a bus 300.

[0059] Here, CPU 301 is responsible for the overall control of log management server 201. CPU 301 may have multiple cores. Memory 302 has, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), and a flash ROM. Specifically, for example, the flash ROM stores an OS program, the ROM stores application programs, and the RAM is used as a work area for CPU 301. The programs stored in memory 302 are loaded into CPU 301 to cause CPU 301 to execute the coded processes.

[0060] The disk drive 303 controls reading / writing data from / to the disk 304 under the control of the CPU 301. The disk 304 stores data written under the control of the disk drive 303. The disk 304 is, for example, a magnetic disk, an optical disk, etc. The database 220 shown in Fig. 2 is realized by, for example, storage devices such as the memory 302 and the disk 304.

[0061] The communication I / F 305 is connected to the network 210 through a communication line, and is connected to an external computer (e.g., the processing devices M1 to Mm shown in FIG. 2) via the network 210. The communication I / F 305 manages the interface between the network 210 and the inside of the device, and controls input and output of data from the external computer. The communication I / F 305 is, for example, a modem or a LAN adapter.

[0062] The portable recording medium I / F 306 controls reading / writing of data from / to the portable recording medium 307 under the control of the CPU 301. The portable recording medium 307 stores data written under the control of the portable recording medium I / F 306. The portable recording medium 307 is, for example, a CD (Compact Disc)-ROM, a DVD (Digital Versatile Disk), or a USB (Universal Serial Bus) memory.

[0063] In addition to the above-mentioned components, the log management server 201 may have, for example, an input device, a display, etc. Also, the log management server 201 may not have, for example, the portable recording medium I / F 306 and the portable recording medium 307 among the above-mentioned components. Also, the processing devices M1 to Mm shown in FIG. 2 can be realized by the same hardware configuration as the log management server 201.

[0064] (Example of functional configuration of log management server 201) Next, an example of the functional configuration of the log management server 201 will be described.

[0065] FIG. 4 is a block diagram showing an example of a functional configuration of the log management server 201. In FIG. 4, the log management server 201 includes a collection unit 401, a log structuring unit 402, a determination unit 403, and an adjustment unit 404. The collection unit 401 to the adjustment unit 404 are functions that become the control unit 400, and specifically, the functions are realized by causing the CPU 301 to execute a program stored in a storage device such as the memory 302, the disk 304, or the portable recording medium 307 shown in FIG. 3, or by the communication I / F 305. The processing results of each functional unit are stored in a storage device such as the memory 302 or the disk 304. To explain in more detail, for example, each functional unit (the collection unit 401 to the adjustment unit 404) is realized by the control plane C shown in FIG. 2.

[0066] The collection unit 401 collects telemetry data from each service #i. Here, the telemetry data is information related to the processing executed in the service #i, and is used to observe the behavior of the service #i. The telemetry data is used, for example, to check the normality of a system or application, analyze performance, and improve the performance.

[0067] There are multiple types of telemetry data. The type of data is determined, for example, depending on the viewpoint from which the behavior of the service #i is observed. Examples of the data types include events, metrics, logs, and traces.

[0068] An event is a record of an individual request or action that occurred at a certain time. For example, an event indicates information such as service #i executed a process or service #i received an instruction, along with time information. Events are used for analysis such as what action or item triggered a problem.

[0069] Metrics are numerical information measured, tabulated, etc., regarding the execution of service #i in processing device Mi. Metrics are, for example, measurements of totals or averages within a certain period of time, such as the utilization rates of CPU, memory, disk, etc., or the number of requests per unit second. Metrics are used to analyze the behavior of service #i per unit time or the periodic behavior of service #i.

[0070] A log is information generated by a system when individual operations are performed within an application or platform. A log is a detailed record of operations that occurred at a specific time. Text messages such as errors and warnings may be output as logs. Logs are used to analyze detailed situations such as which line of a program an error occurred on and what type of error occurred at the time of a failure.

[0071] A trace is information that indicates the transition of the order in which services are called when a request is processed across multiple services. A trace is a mechanism for understanding the order in which services were called and the status of the processing of each service. For example, a trace is used to identify problem areas among services that are linked in a complex manner.

[0072] Specifically, for example, the collection unit 401 collects telemetry data related to each service #i by receiving telemetry data transmitted from the data plane #i of each processing device Mi. The collected telemetry data is temporarily stored in a buffer pool provided on the memory 302, for example.

[0073] The log structuring unit 402 structures the collected telemetry data (log information). Structuring refers to creating a structured log by grouping together telemetry data with the same request ID. First, the log structuring unit 402 acquires a group of telemetry data that includes the same request ID from the collected telemetry data. Then, the log structuring unit 402 creates a structured log for the acquired group of telemetry data.

[0074] Specifically, for example, the log structuring unit 402 refers to the data type of each of the acquired telemetry data groups, extracts a predetermined portion of information from the telemetry data groups, and creates formatted log information that includes the extracted portion of information.

[0075] The predetermined part of information includes, for example, information on a process that is the starting point of an operation according to a request, extracted from telemetry data of an event, and a request ID. The information on the process that is the starting point of an operation is, for example, a timestamp, a message, a method, etc. The request ID is a request ID that is commonly included in each telemetry data group.

[0076] The part of information may also include, for example, information extracted from log and trace telemetry data that indicates the transition of microservices that operated in response to a request (which services were called in what order).The part of information may also include, for example, metrics data (numerical information) extracted from metrics telemetry data when the operation in response to a request ends (completion).

[0077] The part of the information may also include, for example, a status code extracted from telemetry data of the metrics when the operation corresponding to the request is ended (completed.) The status code is, for example, a status code of HTTP (Hypertext Transfer Protocol).

[0078] The part of information may also include, for example, information that is extracted from telemetry data of a log and that is input during a process executed in response to a request (any process of a series of processes identified by a request ID). The part of information may also include, for example, information on the operation of the microservice that made the last transition, extracted from telemetry data of a log.

[0079] Furthermore, the log structuring unit 402 searches for error information and warning information from the acquired telemetry data group. Here, error information is information indicating the occurrence of an error. Warning information is information indicating the occurrence of an event that may be the cause of an error. Events that may be the cause of an error include, for example, "long processing time" and "slow response."

[0080] Error information and warning information are included in telemetry data whose data type is, for example, metrics or logs. Error information in the telemetry data is identified by a character string such as "ERROR." Warning information in the telemetry data is identified by a character string such as "WARN."

[0081] The error information may include, for example, a method, a function, a file name, etc. in which an error occurred. The error information may also include, for example, a timestamp when an error occurred, a message, stack trace information, etc. The error information may also include, for example, information indicating a microservice in which an error occurred.

[0082] The warning information includes, for example, a method, a function, a file name, etc. in which an event that may be a cause of an error occurred. The warning information may also include, for example, a timestamp and a message (suspect message) when the event that may be a cause of an error occurred. The warning information may also include, for example, information indicating a microservice in which an event that may be a cause of an error occurred.

[0083] Furthermore, the log structuring unit 402 creates formatted log information including the extracted part of the information. The formatted log information is unique information among telemetry data having the same request ID. In the following description, the formatted log information may be referred to as a "formatted log."

[0084] Furthermore, when error information is searched for in the telemetry data group, the log structuring unit 402 may add the searched error information to the formatted log. Furthermore, when warning information is searched for in the telemetry data group, the log structuring unit 402 may add the searched warning information to the formatted log.

[0085] Then, the log structuring unit 402 groups the telemetry data group and the formatted log into a structured log.

[0086] The determination unit 403 refers to the formatted log included in the structured log and determines the level of the structured log according to a predefined assessment method. Then, the determination unit 403 sets the determined level in the structured log. Here, the level of the structured log is used when adjusting the storage amount of the telemetry data group included in the structured log in the database 220.

[0087] Specifically, for example, the determination unit 403 determines whether the formatted log contains error information and warning information. If the formatted log does not contain either error information or warning information, the determination unit 403 determines that the level of the structured log is "Lv1."

[0088] Furthermore, if the formatting log does not contain error information and contains warning information, the determination unit 403 determines the level of the structured log to be "Lv2." Furthermore, if the formatting log contains error information, the determination unit 403 determines the level of the structured log to be "Lv3."

[0089] To explain in more detail, for example, the determination unit 403 may assign the level of the structured log to Level 2 or Level 3 depending on whether an event that has an impact on traces has occurred. An event that has an impact on traces is not an event that only affects one microservice, but an event that affects other linked microservices, causing a series of processes for a request to be left incomplete.

[0090] The occurrence of an event that affects traces is determined, for example, by error information or warning information. It is possible to arbitrarily set what kind of error information or warning information is used to determine that an event that affects traces has occurred.

[0091] For example, the determination unit 403 may determine that an event that affects the traces has occurred when the formatted log contains at least one piece of error information. Also, the determination unit 403 may determine that an event that affects the traces has occurred when the formatted log contains specific error information. Also, the determination unit 403 may determine that an event that affects the traces has occurred when the formatted log contains specific warning information.

[0092] Furthermore, even if the formatted log contains error information or warning information, the determining unit 403 may determine that no event that may have an effect on the traces has occurred when the operation for the request (the operation related to a series of processes for the request) has been completed normally. Whether the operation for the request has been completed normally can be determined, for example, by the HTTP status code.

[0093] For example, when the determination unit 403 determines that no event that affects the traces has occurred with reference to the formatted log, it determines the level of the structured log to be "Lv2." On the other hand, when the determination unit 403 determines that an event that affects the traces has occurred, it determines the level of the structured log to be "Lv3." Then, the determination unit 403 adds the determined level to the formatted log included in the structured log.

[0094] The adjustment unit 404 adjusts the amount of data stored in the database 220, which is the storage destination of the telemetry data group. Specifically, for example, the adjustment unit 404 stores some or all of the information of the telemetry data group in the database 220 according to the level of the structured log.

[0095] More specifically, for example, the adjustment unit 404 processes the telemetry data group included in the structured log according to the level of the structured log. The level of the structured log (for example, Lv1, Lv2, Lv3) is identified from the formatted log included in the structured log, for example.

[0096] For example, when the level in the formatted log is "Lv1", the adjustment unit 404 deletes the telemetry data group from the structured log. Then, the adjustment unit 404 stores the structured log from which the telemetry data group has been deleted in database Lv1 in the database 220. "Lv1" corresponds to, for example, a case where error information and warning information are not found in the telemetry data group. In this case, only the formatted log for the telemetry data group is stored in database Lv1.

[0097] Furthermore, when the level in the formatted log is "Lv2", the adjustment unit 404 may extract telemetry data of a specific data type from the telemetry data group included in the structured log. The specific data type is, for example, the same data type as the telemetry data including the warning information in the formatted log.

[0098] Assume that the data type of the telemetry data including the warning information is "metrics." In this case, the adjustment unit 404 identifies telemetry data whose data type is "metrics" from the telemetry data group. In addition, the specific data type may be, for example, the same data type as the telemetry data including the error information in the formatted log.

[0099] Next, the adjustment unit 404 deletes the telemetry data other than the specified telemetry data from the telemetry data group included in the structured log. Then, the adjustment unit 404 stores the structured log from which the telemetry data other than the specified telemetry data has been deleted in the database Lv2 in the database 220.

[0100] "Lv2" corresponds to, for example, a case where error information is not found and warning information is found from the telemetry data group. In this case, the identified telemetry data is stored in the database Lv2 together with the formatted log for the telemetry data group. The formatted log includes, for example, warning information.

[0101] Furthermore, when the level in the formatted log is "Lv3", the adjustment unit 404 stores the structured log in database Lv3 in the database 220. "Lv3" corresponds to, for example, a case where error information is searched for in a telemetry data group. In this case, the entire telemetry data group is stored in database Lv3 together with the formatted log.

[0102] The formatted log includes, for example, error information. However, if the level in the formatted log is "Lv3", the adjustment unit 404 does not need to include the error information in the formatted log. If the level in the formatted log is "Lv3", all of the telemetry data groups are stored, so that the error information can be confirmed from the telemetry data groups.

[0103] The telemetry data temporarily stored in the buffer pool on memory 302 is deleted, for example, when a structured log for that telemetry data is stored in database 220. In addition, in the above description, an example has been given in which the level of the structured log is determined to be "Lv2" when the formatted log does not contain error information and contains warning information, and the level of the structured log is determined to be "Lv3" when the formatted log contains error information, but this is not limiting. For example, when the formatted log contains at least one of error information and warning information, determination unit 403 may determine the level of the structured log to be "Lv3."

[0104] (Example of operation of information processing system 200) Next, an example of the operation of the information processing system 200 will be described.

[0105] Fig. 5 is an explanatory diagram showing an example of the operation of the information processing system 200. Fig. 5 shows a control plane C operating on the log management server 201, and services #1 to #3 and data planes #1 to #3 operating on processing devices M1 to M3. Services #1 to #3 are microservices in a calling relationship.

[0106] First, the control plane C executes a telemetry data collection process S51. The telemetry data collection process S51 is a process for collecting telemetry data related to each of the services #1 to #3. The telemetry data is, for example, telemetry data for a certain period of time collected by each of the data planes #1 to #3.

[0107] Here, telemetry data whose data type is "metrics" may be referred to as "metrics data", and telemetry data whose data type is "events, logs, and traces other than metrics" may be referred to simply as "logs".

[0108] For example, the control plane C collects telemetry data 501 from the data plane #1. The telemetry data 501 includes metrics data 511 and a log 512 related to the service #1. The control plane C also collects telemetry data 502 from the data plane #2. The telemetry data 502 includes metrics data 521 and a log 522.

[0109] Furthermore, the control plane C collects telemetry data 503 from the data plane #3. The telemetry data 503 includes metrics data 531 and a log 532. Here, the telemetry data groups 501 to 503 are telemetry data groups including the same request ID.

[0110] Next, the control plane C executes a log structuring / determination process S52. The log structuring / determination process S52 is a process for creating a structured log from the telemetry data groups 501 to 503, and determining the level of the created structured log according to a predefined assessment method.

[0111] Then, the control plane C executes a processing / storing process S53. The processing / storing process S53 is a process for adjusting the amount of data stored in the database 220 by processing the telemetry data group included in the structured log according to the level of the structured log.

[0112] For example, when the level of the structured log is "Lv1", the control plane C deletes the telemetry data group from the structured log and stores it in the database Lv1 in the database 220. In this case, only the formatted log in the structured log (for example, the formatted log 541) is stored in the database Lv1.

[0113] Furthermore, when the level of the structured log is "Lv2", the control plane C deletes all but the telemetry data of a specific data type from the telemetry data group in the structured log, and stores the data in database Lv2 in the database 220. Here, the specific data type is assumed to be "metrics". In this case, the formatted log and metrics data in the structured log (for example, the formatted log 551 and the metrics data 552) are stored in database Lv2.

[0114] Furthermore, when the level of the structured log is "Lv3", the control plane C stores the structured log as is in the database Lv3 in the database 220. In this case, the formatted log and the telemetry data group in the structured log (for example, the formatted log 561 and the telemetry data group 562) are stored in the database Lv3.

[0115] (Example of determining the level of structured logs and storing them in DB) Next, an example of determining the level of the structured log and an example of DB storage will be described. However, in the following description, the service configuration example and data sample are simplified for the purpose of explaining the operation of the embodiment.

[0116] Case 1: Example of determining the level of structured logs and storing them in DB First, an example of determining the level of the structured log and an example of DB storage in Case 1 will be described.

[0117] Fig. 6 is an explanatory diagram showing a first operation example of an application. In Fig. 6, as microservices for realizing a certain application (service), service #1 that processes requests from a user and services 2 and 3 that execute operations requested by service #1 are shown. Databases DB_2 and DB_3 in which information is stored are connected to services #2 and #3.

[0118] The operation of the application is, for example, to respond to a request (inventory check) from a user, check the inventory information in the inventory database corresponding to the requested keyword, and return the information to the user. In case 1, we assume that a stock check of "P1 SET" and "P2 SET" is received from the user.

[0119] In case 1, service #1 calls service #2 to check inventory information for “P1 SET” and “P2 SET.” Information (telemetry data) logged for each of services #1 to #3 is collected in one place (control plane C) as telemetry data 600.

[0120] Next, the telemetry data 600 will be described with reference to FIGS. 7A to 7F.

[0121] 7A to 7F are explanatory diagrams showing a first sample example of telemetry data. In Fig. 7A to 7F, telemetry data 600 is a collection of telemetry data. Each piece of telemetry data is, for example, sporadically issued from each service #i, and is collected as the telemetry data 600 in one place (the control plane C shown in Fig. 2).

[0122] Each telemetry data is text data including information on the following items: Timestamp, type, level, Interface Service, Message, method, and Request ID. Timestamp indicates the date and time when each telemetry data was recorded (issued) or the process corresponding to each telemetry data was executed in each service #i.

[0123] Type indicates the type of each telemetry data (EVENT, METRIC, LOG, TRACE). EVENT corresponds to event. METRIC corresponds to metrics. LOG corresponds to log. TRACE corresponds to trace. Level indicates the level (log level) of each telemetry data. Examples of the levels of each telemetry data include INFO, WARN, and ERROR.

[0124] INFO indicates information. WARN indicates a warning such as a potential problem. ERROR indicates an error such as a serious failure. Interface Service indicates the service that issued each telemetry data. Message indicates the message issued by service #i. Method indicates the method executed by service #i. Request ID is the request ID included in each telemetry data.

[0125] The telemetry data 600 is telemetry data (log information) related to requests for checking the stock of "P1 SET" and "P2 SET" arranged in chronological order by request ID. The telemetry data group 710 for request ID "19690317-s5888y-123456" is telemetry data related to the stock check of "P1 SET". Furthermore, the telemetry data group 720 for request ID "19690317-s5888y-123466" is telemetry data related to the stock check of "P2 SET".

[0126] The control plane C acquires a group of telemetry data including the same request ID from the telemetry data 600. Next, the control plane C creates a formatted log from the acquired group of telemetry data.

[0127] Here, an example of creating a formatted log will be described, focusing on the telemetry data group 710 including the request ID "19690317-s5888y-123456."

[0128] 8A and 8B are explanatory diagrams showing a first example of creating a formatted log. In Fig. 8A, the control plane C creates a context 800 for forming a unique log format for a user request for inventory check of "P1 SET" from the telemetry data group 710. The context 800 corresponds to the content of the formatted log.

[0129] First, the control plane C extracts information on the process that is the starting point of the operation according to the request from the telemetry data of Type "EVENT" in the telemetry data group 710. Here, the timestamp of the "get contents method (inventory check)" of the "db query" and the request ID "19690317-s5888y-123456" are extracted from the method of (1A) type "EVENT".

[0130] Next, the control plane C extracts information indicating the transition of the service #i that operated in response to the request from the telemetry data of Type "LOG, TRACE" in the telemetry data group 710. Here, the information "SERVICE1, SERVICE2, SERVICE1" indicating the transition of the microservices that operated (1B), (1C), and (1D) is extracted. SERVICE1 corresponds to service #1. SERVICE2 corresponds to service #2.

[0131] Next, control plane C extracts the input information from the telemetry data of Type "LOG" in telemetry data group 710. Here, (1E) "P1 SET" is extracted. Next, control plane C extracts information on the operation of service #i that last transitioned from the telemetry data of Type "LOG" in telemetry data group 710. Here, information on the operation of (1F) "01805" is extracted.

[0132] Next, the control plane C extracts information on when the operation corresponding to the request is ended (completed) from the telemetry data of Type "METRIC" in the telemetry data group 710. Here, the information extracted is the timestamp of the completion flag of the (1G) operation, the metric data (total duration), and the status code.

[0133] In addition, the control plane C extracts the ID of the requesting user as other information from the telemetry data of Type “LOG” in the telemetry data group 710. In this case, (1H) “request user_id 752.254.211.38” is extracted.

[0134] Furthermore, the control plane C searches for error information and warning information from the telemetry data group 710. Error information is identified, for example, from the level "ERROR." Warning information is identified, for example, from the level "WARN." Here, error information and warning information are not searched for from the telemetry data group 710.

[0135] 8B, the control plane C creates a formatted log 801 from the context 800. The control plane C sets the telemetry data group 710 and the formatted log 801 together to create a structured log (here, referred to as a "structured log LG1").

[0136] Next, the control plane C refers to the formatted log 801 and judges the level of the structured log LG1 according to a predefined assessment method. Here, if the formatted log 801 does not contain any error information or warning information, the level is set to "Lv1." If the formatted log 801 contains only warning information, it is assumed that no event that affects the traces has occurred, and the level is set to "Lv2." If the formatted log 801 contains error information, it is assumed that an event that affects the traces has occurred, and the level is set to "Lv3."

[0137] The formatted log 801 does not include any error information or warning information. Therefore, the control plane C determines that the level of the structured log LG1 is "Lv1." The control plane C then sets the determined level "Lv1" in the formatted log 801 (part 802 in FIG. 8B).

[0138] Next, a storage example of the structured log LG1 will be described with reference to FIG.

[0139] Fig. 9 is an explanatory diagram showing a first storage example of a structured log. In Fig. 9, the control plane C adjusts the amount of telemetry data group 710 in the structured log LG1 stored in the database 220. Specifically, for example, the control plane C processes the telemetry data group 710 included in the structured log LG1 according to the level in the formatted log 801.

[0140] In this case, since the level in the formatted log 801 is "Lv1", the control plane C deletes the telemetry data group 710 from the structured log LG1. Then, the control plane C stores the structured log LG1 from which the telemetry data group 710 has been deleted in the database Lv1 in the database 220.

[0141] Next, an example of creating a formatted log will be described with attention to the telemetry data group 720 including the request ID "19690317-s5888y-123466."

[0142] 10A and 10B are explanatory diagrams showing a second example of creating a formatted log. In Fig. 10A, the control plane C creates a context 1000 for forming a unique log format for a user request for inventory check of "P2 SET" from the telemetry data group 720. The context 1000 corresponds to the content of the formatted log.

[0143] First, the control plane C extracts information on the process that is the starting point of the operation according to the request from the telemetry data of Type "EVENT" in the telemetry data group 720. Here, the timestamp of the "get contents method (inventory check)" of the "db query" and the request ID "19690317-s5888y-123466" are extracted from the method of (2A) type "EVENT".

[0144] Next, the control plane C extracts information indicating the transition of the service that was operated in response to the request from the telemetry data of type "LOG, TRACE" in the telemetry data group 720. Here, information "SERVICE1, SERVICE2, SERVICE1" indicating the transition of the service that was operated is extracted from the telemetry data of type "LOG" and type "TRACE" in the telemetry data group 720 (2B), (2C), and (2D).

[0145] Next, control plane C extracts the input information from the telemetry data of Type "LOG" in telemetry data group 720. Here, (2E) "P2 SET" is extracted. Next, control plane C extracts information on the operation of service #i that last transitioned from the telemetry data of Type "LOG" in telemetry data group 720. Here, (2F) information on the operation of "01809" is extracted.

[0146] Next, the control plane C extracts information on when the operation corresponding to the request is completed from the telemetry data of Type "METRIC" in the telemetry data group 720. Here, the information extracted is the timestamp of the completion flag of the (2G) operation, the metric data (total duration), and the status code.

[0147] In addition, the control plane C extracts the ID of the requesting user as other information from the telemetry data of Type “LOG” in the telemetry data group 720. In this case, (2H) “request user_id 752.254.211.38” is extracted.

[0148] Furthermore, the control plane C searches for error information and warning information from the telemetry data group 720. Here, the telemetry data group 720 is not searched for error information and warning information.

[0149] 10B, the control plane C creates a formatted log 1001 from the context 1000. The control plane C sets the telemetry data group 720 and the formatted log 1001 together to create a structured log (here, referred to as a "structured log LG2").

[0150] Next, the control plane C refers to the formatted log 1001 and determines the level of the structured log according to a predefined assessment method. Here, the formatted log 1001 does not contain any error information or warning information. Therefore, the control plane C determines the level of the structured log to be "Lv1". Then, the control plane C sets the determined level "Lv1" in the formatted log 1001 (part 1002 in FIG. 10B).

[0151] Next, a storage example of the structured log LG2 will be described with reference to FIG.

[0152] Fig. 11 is an explanatory diagram showing a second storage example of the structured log. In Fig. 11, the control plane C adjusts the amount of telemetry data group 720 in the structured log LG2 stored in the database 220. Specifically, for example, the control plane C processes the telemetry data group 720 included in the structured log LG2 according to the level in the formatted log 1001.

[0153] In this case, since the level in the formatted log 1001 is "Lv1", the control plane C deletes the telemetry data group 720 from the structured log LG2. Then, the control plane C stores the structured log LG2 from which the telemetry data group 720 has been deleted in the database Lv1 in the database 220.

[0154] Thus, in case 1, the application starts running normally in response to a user request and a series of processes is completed, and the amount of data sent to database 220 is the smallest among cases 1, 2, and 3 (cases 2 and 3 will be described later).

[0155] Case 2: Example of determining the level of structured logs and storing them in DB Next, an example of determining the level of the structured log and an example of DB storage in case 2 will be described.

[0156] Fig. 12 is an explanatory diagram showing a second operation example of an application. In Fig. 12, similar to case 1, service #1 that processes requests from users and services 2 and 3 that execute operations requested by service #1 are shown. Databases DB_2 and DB_3 in which information is stored are connected to services #2 and #3.

[0157] In case 2, it is assumed that a stock check of "P3 SET" is received from a user. In case 2, service #1 calls service #2 to check the stock information of "P3 SET". Information (telemetry data) logged for each of services #1 to #3 is collected in one place (control plane C) as telemetry data 1200.

[0158] Next, the telemetry data 1200 will be described with reference to FIGS. 13A to 13C.

[0159] 13A to 13C are explanatory diagrams showing a second sample example of telemetry data. In Fig. 13A to 13C, a telemetry data group 1300 is an example of a telemetry data group included in the telemetry data 1200 shown in Fig. 12.

[0160] The telemetry data group 1300 is a chronological arrangement of telemetry data (log information) of the same request ID (19690317-s5888y-123476) related to a stock confirmation request for "P3 SET." The control plane C creates a formatted log from the telemetry data group 1300.

[0161] 14A and 14B are explanatory diagrams showing a second example of creating a formatted log. In Fig. 14A, the control plane C creates a context 1400 for forming a unique log format for a user request for checking the stock of "P3 SET" from the telemetry data group 1300. The context 1400 corresponds to the content of the formatted log.

[0162] First, the control plane C extracts information on the process that is the starting point of the operation in response to the request from the telemetry data of Type "EVENT" in the telemetry data group 1300. Here, the timestamp of the "get contents method (inventory check)" of the "db query" and the request ID "19690317-s5888y-123476" are extracted from the method of (3A) type "EVENT".

[0163] Next, the control plane C extracts information indicating the transition of the service that was operated in response to the request from the telemetry data of type "LOG, TRACE" in the telemetry data group 1300. Here, information "SERVICE1, SERVICE2, SERVICE1" indicating the transition of the service that was operated is extracted from the telemetry data of type "LOG" and type "TRACE" in the telemetry data group 1300 (3B), (3C), and (3D).

[0164] Next, control plane C extracts the input information from the telemetry data of Type "LOG" in telemetry data group 1300. Here, (3E) "P3 SET" is extracted. Next, control plane C extracts information on the operation of service #i that last transitioned from the telemetry data of Type "LOG" in telemetry data group 1300. Here, (3F) information on the operation of "01813" is extracted.

[0165] Next, the control plane C extracts information on when the operation corresponding to the request is completed from the telemetry data of Type “METRIC” in the telemetry data group 1300. Here, the timestamp of the completion flag of the (3G) operation and the metric data (total duration) are extracted.

[0166] Furthermore, the control plane C searches for error information and warning information from the telemetry data group 1300. Here, warning information (level "WARN") is searched for from the (3G) telemetry data group 1300, and the status code (status_code: delay) of the telemetry data including the warning information is extracted.

[0167] Furthermore, the control plane C extracts the ID of the requesting user as other information from the telemetry data of Type “LOG” in the telemetry data group 1300. In this case, (3H) “request user_id 752.254.211.38” is extracted.

[0168] 14B, the control plane C creates a formatted log 1401 from the context 1400. The control plane C sets the telemetry data group 1300 and the formatted log 1401 together to create a structured log (here, referred to as a "structured log LG3").

[0169] Next, the control plane C refers to the formatted log 1401 and judges the level of the structured log LG3 according to a predefined assessment method. Here, the formatted log 1401 contains warning information. Although there is warning information, the processing for the user request to check the stock of "P3 SET" has been completed, and it can be said that this is not an event that will affect linked services. The completion of the processing for the user request is identified, for example, from the status code "ok".

[0170] Therefore, the control plane C determines that the level of the structured log LG3 is “Lv2.” Then, the control plane C sets the determined level “Lv2” in the formatted log 1401 (part 1402 in FIG. 14B).

[0171] Next, a storage example of the structured log LG3 will be described with reference to FIG.

[0172] Fig. 15 is an explanatory diagram showing a third storage example of the structured log. In Fig. 15, the control plane C adjusts the amount of telemetry data group 1300 in the structured log LG3 stored in the database 220. Specifically, for example, the control plane C processes the telemetry data group 1300 included in the structured log LG3 according to the level in the formatted log 1401.

[0173] In this case, since the level in the formatted log 1401 is "Lv2", the control plane C deletes all but the metrics data from the telemetry data group 1300 in the structured log LG3. The metrics data is the same type of telemetry data as the telemetry data containing warning information, and serves as information for identifying suspected locations. As a result, only the metrics data 1501 to 1504 remain from the telemetry data group 1300 in the structured log LG3.

[0174] Then, the control plane C stores the structured log LG3 (the metrics data 1501 to 1504+the formatted log 1401) in the database Lv2 in the database 220.

[0175] In case 2, the operation of an application requested by a user is normally started, and a series of processes is completed, but a processing delay occurs for some reason. In case 2, the data sent to database 220 is a set of metrics data 1501-1504 that is useful for analyzing the part of the delay, and formatted log 1401. In case 2, the amount of data sent to database 220 is smaller than in case 3 described later.

[0176] Case 3: Example of determining the level of structured logs and storing them in DB Next, an example of determining the level of the structured log and an example of DB storage in Case 3 will be described.

[0177] Fig. 16 is an explanatory diagram showing a third operation example of an application. In Fig. 16, similar to case 1, there are shown service #1 that processes requests from users, and services #2 and #3 that execute operations requested by service #1. Databases DB_2 and DB_3 in which information is stored are connected to services #2 and #3.

[0178] In case 3, it is assumed that a stock check of "P8 SET" is received from a user. In case 2, service #1 calls service #3 to check the stock information of "P8 SET". Information (telemetry data) logged for each of services #1 to #3 is collected in one place (control plane C) as telemetry data 1600.

[0179] Next, the telemetry data 1600 will be described with reference to FIGS. 17A to 17C.

[0180] 17A to 17C are explanatory diagrams showing a second sample example of telemetry data. In Fig. 17A to Fig. 17C, a telemetry data group 1700 is an example of a telemetry data group included in the telemetry data 1600 shown in Fig. 16.

[0181] The telemetry data group 1700 is a chronological arrangement of telemetry data (log information) of the same request ID (19690317-s5888y-123486) related to a stock confirmation request for "P8 SET." The control plane C creates a formatted log from the telemetry data group 1700.

[0182] 18A and 18B are explanatory diagrams showing a second example of creating a formatted log. In Fig. 18A, the control plane C creates a context 1800 for forming a unique log format for a user request for checking the stock of "P8 SET" from the telemetry data group 1700. The context 1800 corresponds to the content of the formatted log.

[0183] First, the control plane C extracts information on the process that is the starting point of the operation in response to the request from the telemetry data of Type "EVENT" in the telemetry data group 1700. Here, the timestamp of the "get contents method (inventory check)" of the "db query" and the request ID "19690317-s5888y-123486" are extracted from the method of (4A) type "EVENT".

[0184] Next, the control plane C extracts information indicating the transition of the service that was operated in response to the request from the telemetry data of type "LOG, TRACE" in the telemetry data group 1700. Here, information "SERVICE1, SERVICE3, SERVICE1" indicating the transition of the service that was operated is extracted from the telemetry data of type "LOG" and type "TRACE" in the telemetry data group 1700 (4B), (4C), and (4D).

[0185] Next, control plane C extracts the input information from the telemetry data of Type "LOG" in telemetry data group 1700. Here, (4E) "P3 SET" is extracted. Next, control plane C extracts information on the operation of service #i that last transitioned from the telemetry data of Type "LOG" in telemetry data group 1700. Here, (4F) information on the operation of "01823" is extracted.

[0186] Next, the control plane C extracts information on when the operation corresponding to the request is completed from the telemetry data of Type “METRIC” in the telemetry data group 1700. Here, the timestamp of the completion flag of the (4H) operation and the metric data (total duration) are extracted.

[0187] Furthermore, the control plane C extracts the ID of the requesting user as other information from the telemetry data of Type “LOG” in the telemetry data group 1700. In this case, (4I) “request user_id 752.254.211.38” is extracted.

[0188] Furthermore, the control plane C searches for error information and warning information from the telemetry data group 1700. Here, error information (level "ERROR") is searched for from the (4G) telemetry data group 1700, and information of all telemetry data including the error information (here, the contents of method) is extracted. Furthermore, warning information (level "WARN") is searched for from the (4H) telemetry data group 1700, and the status code (status_code: timeover) of the telemetry data including the warning information is extracted.

[0189] 18B, the control plane C creates a formatted log 1801 from the context 1800. The control plane C sets the telemetry data group 1700 and the formatted log 1801 together to create a structured log (here, referred to as "structured log LG4").

[0190] Next, the control plane C refers to the formatted log 1801 and judges the level of the structured log LG4 according to a predefined assessment method. Here, the formatted log 1801 contains error information. Also, the processing of the user request for checking the stock of "P8 SET" is incomplete, which can be said to be an event that affects linked services. The incompletion of the processing of the user request can be identified, for example, from the status code "timeover."

[0191] Therefore, the control plane C determines that the level of the structured log LG4 is “Lv3.” Then, the control plane C sets the determined level “Lv3” in the formatted log 1801 (part 1802 in FIG. 18B).

[0192] Next, a storage example of the structured log LG4 will be described with reference to FIG.

[0193] Fig. 19 is an explanatory diagram showing a fourth storage example of the structured log. In Fig. 19, the control plane C adjusts the amount of telemetry data group 1700 in the structured log LG4 stored in the database 220. Specifically, for example, the control plane C processes the telemetry data group 1700 included in the structured log LG4 according to the level in the formatted log 1801.

[0194] Here, since the level in the formatted log 1801 is "Lv3", the control plane C leaves all of the telemetry data group 1700 in the structured log LG3. Then, the control plane C stores the structured log LG4 (the telemetry data group 1700+the formatted log 1801) in the database Lv3 in the database 220.

[0195] In case 3, the operation of an application requested by a user is terminated as incomplete due to a failure. In case 3, since the processing is incomplete due to some factor, the data sent to the database 220 is a set of all of the telemetry data group 1700 useful for identifying and analyzing the location of the failure and the formatted log 1801.

[0196] (Log management process procedure of the log management server 201) Next, the log management process procedure of the log management server 201 will be described with reference to FIGS.

[0197] 20 and 21 are flowcharts showing an example of a log management process procedure of the log management server 201. In the flowchart of Fig. 20, first, the log management server 201 collects telemetry data from each service #i (step S2001). The collected telemetry data is temporarily stored in a buffer pool provided on the memory 302, for example.

[0198] Next, the log management server 201 acquires a group of telemetry data including the same request ID from the collected telemetry data (step S2002). Then, the log management server 201 executes a formatting process on the acquired group of telemetry data (step S2003).

[0199] The formatting process is a process for creating formatted log information (formatted log) for a group of telemetry data. A specific procedure for the formatting process will be described later with reference to FIGS.

[0200] Next, the log management server 201 creates a structured log that is a set of the formatted log and the telemetry data group (step S2004).Then, the log management server 201 refers to the formatted log in the structured log and determines whether there is any error information or warning information (step S2005).

[0201] If there is neither error information nor warning information (step S2005: Yes), the log management server 201 determines the level of the structured log to be "Lv1" (step S2006), and proceeds to step S2010.

[0202] On the other hand, if there is at least one of error information and warning information (step S2005: No), the log management server 201 judges whether an event that will have an effect on the traces has occurred (step S2007). For example, if there is error information, the log management server 201 judges that an event that will have an effect on the traces has occurred. Also, if there is warning information but no error information, the log management server 201 judges that an event that will have an effect on the traces has not occurred.

[0203] If no influential event has occurred between the traces (step S2007: No), the log management server 201 determines that the level of the structured log is "Lv2" (step S2008), and proceeds to step S2010.

[0204] On the other hand, if an event that has an effect on the traces has occurred (step S2007: Yes), the log management server 201 determines the level of the structured log to be "Lv3" (step S2009).Then, the log management server 201 adds level information indicating the determined level to the formatted log in the structured log (step S2010), and proceeds to step S2101 shown in FIG.

[0205] In the flowchart of FIG. 21, first, the log management server 201 refers to the formatted log in the structured log and determines whether the level of the structured log is "Lv1" (step S2101).

[0206] If the result is "Lv1" (step S2101: Yes), the log management server 201 deletes the telemetry data set from the structured log to create a structured log Lv1 set (step S2102). Then, the log management server 201 stores the structured log Lv1 set in the database Lv1 in the database 220 (step S2103), and ends the series of processes according to this flowchart.

[0207] Also, in step S2101, if the level is not "Lv1" (step S2101: No), the log management server 201 refers to the formatted log in the structured log and determines whether the level of the structured log is "Lv2" (step S2104).

[0208] If it is "Lv2" (step S2104: Yes), the log management server 201 deletes the telemetry data other than the metrics data from the telemetry data group in the structured log to create a structured log Lv2 set (step S2105). Then, the log management server 201 stores the structured log Lv2 set in the database Lv2 in the database 220 (step S2106), and ends the series of processes according to this flowchart.

[0209] Also, in step S2104, if it is not "Lv2" (step S2104: No), the log management server 201 sets the entire structured log as a structured log Lv3 set (step S2107). Then, the log management server 201 stores the structured log Lv3 set in the database Lv3 in the database 220 (step S2108), and ends the series of processes according to this flowchart.

[0210] This enables the log management server 201 to adjust the amount of telemetry data collected from each service #i stored in the database 220. Note that the process from step S2003 onwards is executed for each group of telemetry data including the same request ID acquired in step S2002, for example.

[0211] Next, a specific procedure for the formatting process in step S2003 will be described with reference to FIGS.

[0212] 22 and 23 are flowcharts showing an example of a specific procedure of the formatting process. In the flowchart of Fig. 22, first, the log management server 201 extracts operation start point information from event data in the telemetry data group (step S2201).

[0213] The event data is telemetry data of type "EVENT." The start information of the operation includes, for example, a request ID, a timestamp of the event that is the start of the operation, a message, a method, etc. Then, the log management server 201 adds the start information of the operation to the context (step S2202).

[0214] Next, the log management server 201 extracts operation transition information from the log / trace data of the telemetry data group (step S2203). The log / trace data is telemetry data of type "LOG" and telemetry data of type "TRACE". The operation transition information is information that indicates the transition of a microservice that operates in response to a starting event.

[0215] Then, the log management server 201 adds the operation transition information to the context (step S2204). Next, the log management server 201 searches for error information from the telemetry data group (step S2205). For example, the log management server 201 searches for log data of level "ERROR".

[0216] Then, the log management server 201 judges whether or not error information has been found (step S2206). If no error information has been found (step S2206: No), the log management server 201 proceeds to step S2208.

[0217] On the other hand, if error information is found (step S2206: Yes), the log management server 201 adds the found error information to the context (step S2207). Next, the log management server 201 searches for warning information from the telemetry data group (step S2208). For example, the log management server 201 searches for metrics data of level "WARN". The metrics data is telemetry data of type "METRIC".

[0218] Then, the log management server 201 judges whether or not warning information has been found (step S2209). If warning information has not been found (step S2209: No), the log management server 201 proceeds to step S2301 shown in Fig. 23. On the other hand, if warning information has been found (step S2209: Yes), the log management server 201 adds the found warning information to the context (step S2210) and proceeds to step S2301 shown in Fig. 23.

[0219] In the flowchart of Fig. 23, first, the log management server 201 extracts input information associated with a request ID from a telemetry data group (step S2301). The input information is identified from, for example, a character string "input". Then, the log management server 201 adds the input information to a context (step S2302).

[0220] Next, the log management server 201 extracts the last operation information associated with the request ID from the telemetry data group (step S2303). The last operation information is information on the operation of the microservice that last transitioned. Then, the log management server 201 adds the last operation information to the context (step S2304).

[0221] Next, the log management server 201 extracts metrics information at the time when the operations related to the series of processes are completed from the telemetry data group (step S2305). The metrics information includes, for example, a timestamp at the time when the operations related to the series of processes are completed, a completion flag, metrics (numerical data), a status code, etc. Then, the log management server 201 adds the metrics information to the context (step S2306).

[0222] Next, the log management server 201 extracts other information from the telemetry data group (step S2307). The other information is, for example, IP (Internet Protocol) addresses of the server and client, a user ID, etc. The log management server 201 adds the other information to the context (step S2308).

[0223] Then, the log management server 201 references the context, generates a formatted log for the telemetry data group (step S2309), and returns to the step that called the formatting process.

[0224] This enables the log management server 201 to generate a formatted log that is unique information among telemetry data having the same request ID.

[0225] As described above, the log management server 201 according to the embodiment can acquire a group of telemetry data including the same request ID from the telemetry data collected from each service #i of the services #1 to #m. The telemetry data is observation information related to the processing executed in each service #i. Furthermore, the log management server 201 can search for error information and warning information from the acquired group of telemetry data. The error information indicates the occurrence of an error. The warning information indicates the occurrence of an event that may be the cause of the error. Then, the log management server 201 can store some or all of the information from the group of telemetry data in the database 220, which is the storage destination, depending on the search result.

[0226] This allows the log management server 201 to adjust the amount of telemetry data stored in the database 220, which is the storage destination. For example, the log management server 201 can adjust whether to store only a portion of the telemetry data group or all of the information, depending on whether error information or warning information is included, for each telemetry data group associated with the same request ID. This allows the log management server 201 to reduce the storage capacity used to store telemetry data in the database 220, while retaining information necessary for application performance evaluation and the like.

[0227] Furthermore, the log management server 201 can refer to the data types of each telemetry data group including telemetry data of different data types, and extract a predetermined portion of information from the telemetry data group, thereby creating a formatted log (formatted log information) including the extracted portion of information. The data types are, for example, events, metrics, logs, and traces. Furthermore, the log management server 201 can store only the created formatted log for the telemetry data group in the database 220 (for example, database Lv1) if no error information or warning information is found from the telemetry data group.

[0228] As a result, the log management server 201 can reduce the amount of storage in the database 220 by storing only the minimum amount of information required by an analyst (a predetermined portion of information) for a group of telemetry data when the system is operating normally and a series of processes is completed, in order to identify the processing performed in response to a request.

[0229] Furthermore, according to the log management server 201, when error information is not found and warning information is found from the telemetry data group, it is possible to identify telemetry data of the same data type as the telemetry data containing the warning information from the telemetry data group. Then, according to the log management server 201, it is possible to store the identified telemetry data together with the formatted log for the telemetry data group in the database 220 (for example, database Lv2).

[0230] As a result, when an event that may be the cause of an error occurs even though no error has occurred during a series of processes, the log management server 201 stores only information required for analyzing the event, thereby reducing the amount of data stored in the database 220. Also, by storing the formatted log together, the log management server 201 can easily identify the process executed for the request.

[0231] Furthermore, according to the log management server 201, when error information is searched from the telemetry data group, the telemetry data group can be stored in the database 220 (for example, database Lv3) together with the formatted log.

[0232] This allows the log management server 201 to store all of the telemetry data when some error occurs and the system does not operate normally. This allows the log management server 201 to avoid a situation where there is a shortage of information to identify the location of the failure or to investigate the cause when a serious failure occurs. In addition, the log management server 201 can easily identify the process executed for the request by storing the formatted log as well.

[0233] Furthermore, the log management server 201 can extract information on the process that is the starting point of an operation in response to a request and the request ID from the telemetry data of an event in the telemetry data group, and create a formatted log.

[0234] This enables the log management server 201 to identify the process executed in response to a request from the request ID and event information.

[0235] Furthermore, according to the log management server 201, it is possible to extract information representing the transition of a microservice that has operated in response to a request from the log and trace telemetry data in the telemetry data group, and create a formatted log.

[0236] This enables the log management server 201 to identify the microservice that operated in response to the request.

[0237] Furthermore, according to the log management server 201, it is possible to further extract information on the operation of the microservice that last transitioned from the telemetry data of the log among the telemetry data group, and create a formatted log.

[0238] This enables the log management server 201 to check the content of the operation of the microservice that last transitioned when identifying the process executed in response to a request.

[0239] Furthermore, according to the log management server 201, it is possible to further extract, from the telemetry data of the metrics among the telemetry data group, the metrics data at the time when the operation in response to the request is completed, and to create a formatted log.

[0240] This allows the log management server 201 to check the metrics data at the time the operation for the request is completed when identifying the process executed in response to the request.

[0241] Furthermore, according to the log management server 201, it is possible to extract a status code at the time when an operation in response to a request is completed from the telemetry data of metrics among the telemetry data group, and create a formatted log.

[0242] This allows the log management server 201 to check the status code at the time when the operation for the request is completed in identifying the process executed in response to the request.

[0243] Furthermore, according to the log management server 201, when warning information is searched from the telemetry data group, the warning information can be added to the formatted log.

[0244] This enables the log management server 201 to easily check from the formatted log what kind of event (an event that could cause an error) has occurred, without having to check the contents of the telemetry data stored together with the formatted log.

[0245] Furthermore, according to the log management server 201, when error information is searched for from the telemetry data group, the error information can be added to the formatted log.

[0246] This allows the log management server 201 to easily check what kind of error has occurred from the formatted log, without having to check the contents of the telemetry data stored together with the formatted log.

[0247] For these reasons, the log management server 201 can analyze from a structured log whether the processing of an application (system) composed of multiple microservices is normal or a processing in which a failure or abnormality has occurred. As a result, the log management server 201 can reduce the storage capacity used to store telemetry data and reduce the storage area to be secured by storing only the more useful data from among the telemetry data collected to monitor the normality of the processing of the application.

[0248] Furthermore, when constructing database 220 on the cloud, log management server 201 can suppress the amount of data transfer and memory usage of stored data, and therefore can reduce charges and operational costs compared to the conventional case of storing all data. Also, log management server 201 can use different memory areas in database 220 as storage destinations for stored data depending on the level (Lv1, Lv2, Lv3). Therefore, when implementing deletion of stored data or external transfer, log management server 201 makes it possible to easily call up data and perform deletion or transfer.

[0249] The log management method described in this embodiment can be realized by executing a prepared program on a computer such as a personal computer or a workstation. This log management program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, a DVD, or a USB memory, and is executed by being read from the recording medium by the computer. This log management program may also be distributed via a network such as the Internet.

[0250] In addition, the log management device 101 (log management server 201) described in this embodiment can also be realized by application-specific ICs such as standard cells or structured ASICs (Application Specific Integrated Circuits) or PLDs (Programmable Logic Devices) such as FPGAs.

[0251] The following supplementary notes are further disclosed regarding the above-described embodiment.

[0252] (Supplementary Note 1) Obtain a group of observation information including the same request ID that identifies a series of processes executed in response to a request from among observation information regarding processes executed in each microservice of a plurality of microservices, and Searching the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of the error; storing some or all of the observation information group in a storage destination database according to the search results; A log management device comprising a control unit.

[0253] (Appendix 2) The observation information group includes observation information of different data types, The control unit is extracting a predetermined portion of information from the observation information group by referring to the data type of each of the observation information groups, thereby creating formatted log information including the extracted portion of information; if the error information and the warning information are not found from the group of observation information, only the created formatted log information for the group of observation information is stored in the database. 2. A log management device according to claim 1.

[0254] (Additional Note 3) The control unit is if the error information is not found and the warning information is found from the group of observation information, identifying observation information of the same data type as the observation information including the warning information from the group of observation information; storing the identified observation information together with the formatted log information in the database for the group of observation information; 3. A log management device according to claim 2.

[0255] (Additional Note 4) The control unit is if the error information is found from the group of observation information, the group of observation information is stored in the database together with the formatted log information; 4. The log management device according to claim 2 or 3.

[0256] (Additional Note 5) The observation information group includes observation information of at least one data type of events, metrics, logs, and traces, the part of information includes information on a process that is a starting point of an operation in response to the request, the information being extracted from observation information of an event in the group of observation information, and the request ID; 5. The log management device according to claim 2, wherein:

[0257] (Appendix 6) The part of information includes information representing the transition of a microservice that operated in response to the request, the information being extracted from log and trace observation information among the group of observation information; 6. A log management device according to claim 5.

[0258] (Appendix 7) The log management device according to appendix 6, wherein the portion of information includes information on the operation of the microservice that last transitioned, extracted from log observation information among the group of observation information.

[0259] (Appendix 8) The log management device of appendix 6 or 7, characterized in that the portion of information includes metrics data at the time when the operation corresponding to the request is completed, extracted from metric observation information among the group of observation information.

[0260] (Appendix 9) A log management device as described in any one of Appendices 6 to 8, characterized in that the portion of information includes a status code extracted from metric observation information among the group of observation information when the operation corresponding to the request is completed.

[0261] (Supplementary Note 10) The control unit is if the warning information is found from the group of observation information, add the warning information to the formatted log information; 4. A log management device according to claim 3.

[0262] (Additional Note 11) The control unit is if the error information is found from the group of observation information, add the error information to the formatted log information; 5. A log management device according to claim 4.

[0263] (Supplementary Note 12) The control unit is 3. The log management device according to claim 2, wherein, for the group of observation information, only the formatted log information is stored in a first storage area within the database.

[0264] (Supplementary Note 13) The control unit is The log management device described in Appendix 3, characterized in that for the group of observation information, the identified observation information is stored in a second memory area within the database together with the formatted log information.

[0265] (Supplementary Note 14) The control unit is The log management device according to claim 4, further comprising: storing the group of observation information together with the formatted log information in a third memory area within the database.

[0266] (Appendix 15) Obtain a group of observation information including the same request ID that identifies a series of processes executed in response to a request from among observation information of multiple data types related to processes executed in each of the multiple microservices collected from each of the multiple microservices; Searching the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of the error; adjusting the amount of data stored in a database in which the group of observation information is stored according to the search results; A log management method, the processing of which is executed by a computer.

[0267] (Appendix 16) Obtain a group of observation information including the same request ID that identifies a series of processes executed in response to a request from among observation information of multiple data types related to processes executed in each of the multiple microservices collected from each of the multiple microservices; Searching the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of the error; adjusting the amount of data stored in a database in which the group of observation information is stored according to the search results; A log management program that causes a computer to execute a process. [Explanation of symbols]

[0268] 101 Log management device 110,220 Databases 120 Observation Information Set 121~123 Observation Information Group 130 Some information 200 Information Processing Systems 201 Log Management Server 210 Network 300 Bus 301 CPU 302 Memory 303 Disk Drive 304 Disk 305 Communication I / F 306 Portable Recording Media I / F 307 Portable recording media 400 Control section 401 Collection Department 402 Log Structuring Department 403 Judgment section 404 Adjustment section 501,502,503,600,1200,1600 Telemetry Data 562,710,720,1300,1700 Telemetry data set 511,521,531,552,1501,1502,1503,1504 Metrics Data 512,522,532 logs 541,551,561,801,1001,1401,1801 Formatted Log 800,1000,1400,1800 context

Claims

1. Obtaining a group of observation information including a same request ID that identifies a series of processes executed in response to a request from observation information related to processes executed in each of a plurality of microservices, the observation information being collected from each of the microservices; Searching the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of the error; storing some or all of the observation information group in a storage destination database according to the search results; A log management device comprising a control unit.

2. the observation information group includes observation information of different data types, The control unit is extracting a predetermined portion of information from the observation information group by referring to the data type of each of the observation information groups, thereby creating formatted log information including the extracted portion of information; if the error information and the warning information are not found from the group of observation information, only the created formatted log information for the group of observation information is stored in the database.

2. The log management device according to claim 1.

3. The control unit is if the error information is not found and the warning information is found from the group of observation information, identifying observation information of the same data type as the observation information including the warning information from the group of observation information; storing the identified observation information together with the formatted log information in the database for the group of observation information; 3. The log management device according to claim 2.

4. The control unit is if the error information is found from the group of observation information, the group of observation information is stored in the database together with the formatted log information; 3. The log management device according to claim 2.

5. the observation information group includes observation information of at least one data type of an event, a metric, a log, and a trace; the part of information includes information on a process that is a starting point of an operation in response to the request, the information being extracted from observation information of an event in the group of observation information, and the request ID; 5. The log management device according to claim 2, wherein the log management device is a data storage device.

6. The part of information includes information that represents a transition of a microservice that has operated in response to the request, the information being extracted from log and trace observation information among the group of observation information.

6. The log management device according to claim 5.

7. Obtaining a group of observation information including a same request ID that identifies a series of processes executed in response to a request from observation information related to processes executed in each of a plurality of microservices, the observation information being collected from each of the microservices; Searching the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of the error; storing some or all of the observation information group in a storage destination database according to the search results; A log management method, the processing of which is executed by a computer.

8. Obtaining a group of observation information including a same request ID that identifies a series of processes executed in response to a request from observation information related to processes executed in each of a plurality of microservices, the observation information being collected from each of the microservices; Searching the acquired group of observation information for error information indicating the occurrence of an error and warning information indicating the occurrence of an event that may be a cause of the error; storing some or all of the observation information group in a storage destination database according to the search results; A log management program that causes a computer to execute a process.

Citation Information

Patent Citations

  • Maintenance management system and data processing method

    JP2020028005A

  • Systems and Methods for Processing Software Application Notifications

    US20220245017A1

  • Monitoring system, monitoring method, agent program, and manager program

    WO2021095114A1