Root cause analysis system and root cause analysis method in heterogeneous virtualization environment
A root cause analysis system according to an embodiment of the present disclosure may include: an Analysis tool calculator that operates in a microservice environment and calculates a corresponding analysis tool, which is a member of analyzing a root cause of target software, based on comparison software configured of corresponding independent modules, which are independent modules classified by function to correspond to the target software, which is software to be analyzed; and a Cause analyser that analyzes the root cause of an abnormal operation occurring in the target software using the corresponding analysis tool.
1 . A root cause analysis system, comprising:
at least one memory configured to store thereon computer program code; and
at least one processor configured to access the at least one memory and operate according to the computer program code to implement:
an Analysis tool calculator that calculates a corresponding analysis tool, which is a member of analyzing a root cause of target software, among a plurality of pieces of software that operate in a heterogeneous virtualization environment, based on comparison software configured of corresponding independent modules, which are independent modules classified by function to correspond to the target software and executed and managed independently, wherein the target software is software to be analyzed, operates in a microservice environment, and is configured of target independent modules, which are independent modules that are executed and managed independently; and
a Cause analyser that analyzes the root cause of an abnormal operation occurring in the target software using the corresponding analysis tool,
wherein the Analysis tool calculator comprises a Module collector that collects a corresponding independent module from an external server, a Comparison analyser that configures the comparison software by configuring the corresponding independent module identical to a target independent module, a Simulator that simulates the comparison software through a predetermined control method; and a Root analyser that calculates the corresponding analysis tool based on result information, which is data generated while the comparison software is simulated,
wherein, when the Module collector fails to collect the corresponding independent module that matches the target independent module, the Comparison analyser configures the comparison software by including at least one corresponding independent module similar to the target independent module within a scope that a predetermined compensation condition is satisfied.
2 . The system of claim 1 , wherein the Analysis tool calculator further comprises a Date collector that collects the result information composed of log information, metric information, and trace information generated during a simulation process utilizing different data collection members.
3 . The system of claim 2 , wherein the Date collector uses a Fluentd data collection member for the log information, a Prometheus data collection member for the metric information, and a Jaeger data collection member for the trace information.
4 . The system of claim 2 , wherein the Root analyser calculates the corresponding analysis tool by performing deep learning based on the predetermined control method and the result information.
5 . The system of claim 1 , wherein:
the Analysis tool calculator further comprises a Correspondence analyser that calculates a coincidence rate of the result information for the root cause for two pieces of software using a predetermined comparison method; and
wherein the predetermined compensation condition is a condition where the coincidence rate is greater than a predetermined reference.
6 . The system of claim 1 , wherein:
the Analysis tool calculator further comprises a Time predictor that calculates a creation time, which is a time expected for the Root analyser to calculate the corresponding analysis tool through deep learning; and
wherein the Cause analyser comprises a Cause storage where a past analysis tool, which is a member of analyzing the root cause of past software, which is software that operates in a microservice environment in the past, is stored, and a Monitoring unit that selects one of the past analysis tools using a predetermined selection method during the time the corresponding analysis tool is calculated, and analyzes the root cause of the target software based on the selected past analysis tool when a predetermined replacement condition is satisfied.
7 . The system of claim 6 , wherein:
the predetermined replacement condition is a condition in which the creation time exceeds a reference time; and
the Monitoring unit considers a reference time when the comparison software is determined only with the corresponding independent module identical to the target independent module and a reference time when the comparison software is determined to include the corresponding independent module that is similar to and not identical to the target independent module differently from each other.
8 . The system of claim 7 , wherein the predetermined selection method comprises a first selection method selected based on whether detailed information matches in a predetermined order, and a second selection method that selects the highest correspondence rate.
9 . The system of claim 1 , further comprising an Interface calculator that provides a user interface to a requester who has requested root cause analysis of the target software,
wherein the Interface calculator provides a predetermined notification to the requester when a situation occurs in which the comparison software is configured only with the corresponding independent module identical to the target independent module in a state where the Module collector analyzes the root cause of the target software with a trained corresponding analysis tool in a state where the corresponding independent module identical to the target independent module has not been collected.
10 . A root cause analysis method, the method being implemented by a root cause analysis system configured to analyze a root cause of software operating in a microservice environment, the root cause analysis system comprising at least one memory configured to store thereon computer program code; and at least one processor configured to access the at least one memory and operate according to the computer program code, the method comprising:
calculating a corresponding analysis tool, which is a member of analyzing the root cause of target software, among a plurality of pieces of software that operate in a heterogeneous virtualization environment based on comparison software configured of corresponding independent modules, which are independent modules classified by function to correspond to the target software and executed and managed independently, wherein the target software is software to be analyzed, operates in the microservice environment, and is configured of target independent modules, which are independent modules that are executed and managed independently; and
analyzing the root cause of an abnormal operation occurring in the target software utilizing the corresponding analysis tool,
wherein calculating the corresponding analysis tool comprises:
collecting a corresponding independent module from an external server;
configuring the comparison software by configuring the corresponding independent module identical to a target independent module;
simulating the comparison software through a predetermined control method; and
calculating the corresponding analysis tool based on result information, which is data generated while the comparison software is simulated,
wherein the method further comprises, when collecting of the corresponding independent module that matches the target independent module fails, configuring the comparison software by including at least one corresponding independent module similar to the target independent module within a scope that a predetermined compensation condition is satisfied.