System and method for software path tracing and testing for microservices

A business impact range presentation method comprising:

• a test log collection step in which a test log collection unit collects test record information indicating an execution result of a test on monitored software in which one or more operation steps each indicating a component of each content of a plurality of businesses and a plurality of microservices that execute processing by an operation of the one or more operation steps are connected via one or more request paths, and collects test case information indicating a relationship between the content of each of the businesses and each of the operation steps;
• a use case association step in which a use case association unit generates use case association information by associating, based on the test record information and the test case information collected in the test log collection step, a request path corresponding to each of the operation steps among the one or more request paths with the content of each of the businesses;
• a monitoring information acquisition step in which a monitoring information acquisition unit acquires trace data indicating an execution result of each of the microservices as an execution result in a production environment for the monitored software;
• a trace data shaping step in which a trace data shaping unit determines whether a redundant request path exists among the request paths during a normal operation, and creates, when the redundant request path exists, the trace data excluding the redundant request path;
• and
• a business impact range analysis step in which a business impact range analysis unit determines, based on the trace data acquired in the monitoring information acquisition step, whether an abnormality occurs in any request path among the one or more request paths, wherein
• in the business impact range analysis step, when it is determined that the abnormality occurs in the any request path, the business impact range analysis unit refers to the use case association information based on the any request path excluding the redundant request path, and specifies a content of a business impacted by the request path where the abnormality occurs among the content of each of the businesses,
• wherein
• the trace data includes, as a processing time required for processing of each request by each of the operation steps or each of the microservices, a processing time of the each request in each of the request paths, and
• in the business impact range analysis step, the business impact range analysis unit refers to the trace data to compare the processing time of the each request with a set threshold, and when a processing time of any request exceeds the threshold, the business impact range analysis unit determines that the abnormality occurs and analyzes a request path of the request whose processing time exceeds the threshold as a request path where the abnormality occurs and a request path that does not reach a target value, wherein
• in the business impact range analysis step, the business impact range analysis unit refers to the use case association information based on the request path that does not reach the target value, and extracts, each as a request path to be analyzed, all request paths including the request path that does not reach the target value from among the one or more request paths, and wherein
• in the business impact range analysis step, the business impact range analysis unit determines whether the request path to be analyzed exists in the trace data, analyzes, when it is determined that the request path to be analyzed does not exist in the trace data, a content of a business related to each of the microservices connected to the request path to be analyzed among the content of each of the businesses as a content of a business possibly impacted by the request path to be analyzed, and analyzes, when it is determined that the request path to be analyzed exists in the trace data, the content of the business related to each of the microservices connected to the request path to be analyzed among the content of each of the businesses as a content of a business impacted by the request path to be analyzed, and wherein
• the business impact range analysis unit is configured to perform said referring based on the trace data from which the redundant request path has been excluded, such that the content of the business corresponding to the request path where the abnormality occurs is correctly detected without mismatch caused by redundant retry paths.