A microservice management method and device

Abstract

The present invention discloses a microservice management method, the method comprising obtaining microservice resource management data, the microservice resource management data comprising microservice supply and marketing data and microservice orchestration data; obtaining performance data and fault data of each microservice; generating corresponding fault information of each microservice according to a preset microservice call threshold and in combination with the performance data and fault data of each microservice; determining the impact range of each microservice fault information according to the fault information of each microservice and in combination with the resource management data of the microservice. The present invention also discloses a microservice resource management device. The present invention can realize unified management of microservices and more accurately locate microservice faults.

Description

Technical Field

[0001] The present invention belongs to the field of computer software and relates to microservice management technology. Background Art

[0002] Microservice Architecture is an emerging software architecture style that develops an independent and complete application system by developing a number of tiny services. Each microservice is built around business functions and can be independently deployed through an automated deployment mechanism, running in its own process, and using lightweight communication mechanisms between microservices. These microservices can be written in different programming languages, can use different data storage technologies, and maintain minimal centralized management.

[0003] Large-scale microservice systems involve tens of thousands of microservices. Since there may be call dependencies between microservices, any component error may cause a large number of users to be unable to access normally. How to manage a large number of microservices and ensure the service quality of microservices has become a difficult problem.

[0004] Currently, microservices are often managed based on application topology. The specific method is to track the calling relationship between microservices to obtain the application topology, and then locate the service failure point based on the application topology. However, if the microservices are not well organized and managed, the application topology may be a very complex mesh relationship. When the number of microservices is huge, it is impossible to locate the service failure point based on the application topology, nor to determine the impact range of the faulty microservice based on the application topology, resulting in the inability to better manage massive microservices.

[0005] Therefore, how to effectively manage microservices and accurately determine the impact scope of faulty microservices has become an urgent problem to be solved. Summary of the invention

[0006] The purpose of the present invention is to provide a technical means to effectively and accurately determine the impact scope of a faulty microservice, so as to achieve the purpose of effectively managing microservices.

[0007] In order to achieve the above object, the present invention provides a microservice management method, the method comprising:

[0008] Acquire microservice resource management data, wherein the microservice resource management data includes microservice supply and marketing data and microservice orchestration data;

[0009] Obtain performance data and fault data for each microservice;

[0010] According to the preset microservice call threshold, combined with the performance data and fault data of each microservice, corresponding fault information of each microservice is generated;

[0011] The impact scope of each microservice fault information is determined according to the fault information of each microservice in combination with resource management data of the microservice.

[0012] Further:

[0013] The microservice supply and marketing data includes microservice provider information and microservice orderer information;

[0014] The microservice orchestration data includes service information and service flow information provided by the microservice.

[0015] Further:

[0016] The performance data of each microservice includes the call time, call delay, number of calls, and number of successful calls of the microservice;

[0017] The fault data of each microservice includes the time when the microservice fault occurred and the fault content.

[0018] Specifically, the method for generating corresponding fault information of each microservice according to the preset microservice call threshold and combining the performance data and fault data of each microservice is as follows:

[0019] Preset microservice call success rate threshold and call delay threshold;

[0020] Obtain an average call delay of the microservice according to the call time and call delay of the microservice, and obtain a call success rate of the microservice according to the number of calls and the number of successful calls of the microservice;

[0021] When the microservice call success rate or call delay exceeds the microservice call success rate threshold and the call delay threshold, microservice fault information is generated according to the microservice call time in combination with the microservice orchestration data.

[0022] Specifically, the method for determining the impact scope of each microservice fault information according to the microservice fault information combined with the resource management data of the microservice is specifically:

[0023] Acquire service flow information in the microservice orchestration data according to the microservice fault information;

[0024] Acquire service information provided by the microservice according to the service flow information;

[0025] Acquire the microservice subscriber information according to the service information provided by the microservice;

[0026] The microservice ordering party information is determined to be an impact scope of the microservice fault information.

[0027] The present invention also provides a microservice management device, the device comprising:

[0028] A microservice resource management unit, used to obtain and manage microservice resource management data, wherein the microservice resource management data includes microservice supply and marketing data and microservice orchestration data;

[0029] Data collection unit, used to obtain performance data and fault data of each microservice;

[0030] A fault information generating unit, configured to generate corresponding fault information of each microservice according to a preset microservice call threshold value and in combination with the performance data and fault data of each microservice collected by the data collecting unit;

[0031] The impact analysis unit is used to determine the impact scope of each microservice fault information based on the microservice fault information generated by the fault information generation unit and the fault data collected by the data collection unit in combination with the microservice resource management data acquired by the microservice resource management unit.

[0032] Specifically, the microservice resource management unit further includes:

[0033] A microservice supply and marketing data management module, used to obtain and manage the microservice provider information and microservice orderer information contained in the microservice supply and marketing data;

[0034] The microservice orchestration data management module is used to obtain and manage the service information and service flow information provided by the microservices contained in the microservice orchestration data.

[0035] Specifically, the data collection unit further includes:

[0036] A performance data collection module is used to collect the call time, call delay, number of calls, and number of successful calls of each microservice;

[0037] The fault data collection module is used to collect the fault occurrence time and fault content of each microservice.

[0038] Specifically, the fault information generating unit further comprises:

[0039] Threshold setting module, used to preset microservice call success rate threshold and call delay threshold;

[0040] A calculation module is used to obtain an average call delay of the microservice according to the call time and call delay of the microservice, and obtain a call success rate of the microservice according to the number of calls and the number of successful calls of the microservice;

[0041] The fault information generating module is used to generate microservice fault information according to the microservice call time in combination with the microservice orchestration data when the microservice call success rate or call delay calculated by the calculating module exceeds the microservice call success rate threshold and call delay threshold set by the threshold setting module.

[0042] Specifically, the impact analysis unit further includes:

[0043] A service flow information acquisition module, configured to acquire service flow information in the microservice orchestration data according to the microservice fault information generated by the fault information generation module and the fault data collected by the data collection unit;

[0044] A service information acquisition module, used to acquire service information provided by the microservice according to the service flow information acquired by the service flow information acquisition module;

[0045] An ordering information acquisition module, which acquires the microservice ordering party information according to the service information provided by the microservice acquired by the service information acquisition module;

[0046] The impact scope determination module is used to determine the impact scope of the microservice fault information according to the microservice ordering party information obtained by the ordering information acquisition module.

[0047] The present invention discloses a microservice management method and device, which obtains the corresponding relationship between microservices, clients, and service flows through the ordering information and orchestration information registered by microservices, finds the service flow corresponding to the faulty microservice based on the collected microservice performance data and fault data, and then obtains the client corresponding to the service flow, and accurately locates the scope of the fault impact. This technology does not need to obtain a complex microservice mesh structure to simply and accurately locate the fault point, greatly reducing the management cost of microservices and improving management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0049] Figure 1 A schematic diagram of a method flow of a microservice management method provided in Example 1 of the present application;

[0050] Figure 2 A flow chart of the method provided in Example 2 of the present application;

[0051] Figure 3A flow chart of the method provided in Example 3 of the present application;

[0052] Figure 4 This is a structural diagram of a microservice management device according to Embodiment 5 of the present application;

[0053] Figure 5 This is a structural diagram provided for Example 6 of the present application. DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0055] The specific implementation of the present invention is further described in detail below in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0056] like Figure 1 As shown, it is a method flow chart of inventing a microservice management method, and this example includes the following steps:

[0057] Step S01: Acquire microservice resource management data, wherein the microservice resource management data includes microservice supply and marketing data and microservice orchestration data.

[0058] The microservice supply and marketing data includes microservice provider information and microservice orderer information.

[0059] The provider information includes the provider name and service ID, and the subscriber information includes the subscriber name and the subscriber service ID.

[0060] The microservice orchestration data includes service information and service flow information provided by the microservice.

[0061] Some services in a microservice can be service flows composed of other services in sequence; and a service flow can also contain services and other service flows. These microservice orchestration data can be obtained from the microservice orchestrator, which can directly reflect the correspondence between services and service flows.

[0062] Step S02: Obtain performance data and fault data of each microservice.

[0063] Performance data is data that reflects the performance of microservices, including service ID, statistical start time, statistical end time, number of calls to the service, number of successful calls, etc.

[0064] Fault data refers to data that reflects microservice faults, including service ID, occurrence time, fault title, fault text, etc.

[0065] Step S03: Generate corresponding microservice fault information according to the preset microservice call threshold and in combination with the performance data and fault data of each microservice.

[0066] In actual applications, the microservice itself does not send out fault information, but the probability of unsuccessful calls is high, and there may be a fault. Therefore, the accuracy of microservice fault judgment is ensured based on the success of the microservice call to evaluate whether a fault has occurred.

[0067] Step S04: Determine the impact scope of each microservice fault information according to the microservice fault information and the resource management data of the microservice.

[0068] Through the service identifier of the microservice, the service flow corresponding to the service can be obtained. Through the services in the service flow, the customers who subscribe to these services can be obtained, and then the impact scope of these customers for the microservice failure can be determined.

[0069] It can be seen that the embodiment of the present invention discloses a microservice management method, which obtains the supply and marketing data and orchestration data of the microservices, combines the obtained microservice performance data and fault data, finds the relationship of the microservice flows, and determines which microservices are affected by the fault according to the relationship of the microservice flows. The present invention can determine the impact range of the faulty microservice without obtaining the application topology relationship of the microservices, and can manage the microservice IT system more effectively.

[0070] In order to better illustrate the present invention, a second embodiment is given to explain in detail the method of generating fault information of each microservice. Figure 2 shown.

[0071] Step S201: Preset a microservice call success rate threshold and a call delay threshold.

[0072] Set the call success threshold and call delay threshold based on experience.

[0073] The call success threshold and call delay threshold can also be adjusted according to the actual situation to accurately reflect the failure of the microservice.

[0074] Step S202: obtaining an average call delay of the microservice according to the call time and call delay of the microservice, and obtaining a call success rate of the microservice according to the number of calls and the number of successful calls of the microservice.

[0075] The average call delay is the average of the delays of each call;

[0076] The call success rate is obtained by dividing the number of successful calls by the number of calls.

[0077] Step S203: When the microservice call success rate or call delay exceeds the microservice call success rate threshold and the call delay threshold, microservice fault information is generated according to the microservice call time in combination with the microservice orchestration data.

[0078] In addition to the fault information reported by the microservice itself, this method also determines whether a microservice fails based on the call success rate of the microservice, thereby more accurately determining the time of occurrence and impact range of the fault.

[0079] In order to better illustrate the present invention, a third embodiment is given to explain in detail the method of generating fault information of each microservice. Figure 3 shown.

[0080] Step S301: Obtain service flow information in the microservice orchestration data according to the microservice fault information.

[0081] Step S302: Acquire service information provided by the microservice according to the service flow information.

[0082] Step S303: Acquire the microservice subscriber information according to the service information provided by the microservice.

[0083] Step S304: Determine that the microservice ordering party information is the impact scope of the microservice fault information.

[0084] Through this technical solution, it is convenient to obtain the service flow information in the orchestration data of this microservice through the microservice fault information, determine which service information is included in the service flow, and then obtain the service provider and subscriber information, and then determine that these subscribers are the scope affected by the fault information. This method is simple and fast, and can make a judgment without knowing the topology information of the entire microservice, saving the management cost of microservices and improving efficiency.

[0085] In order to better illustrate the present invention, a fourth embodiment of the present invention is given in combination with examples to explain the method steps for determining the scope of a microservice failure.

[0086] Get the resource management data of microservices, including microservice supply and marketing data and microservice orchestration data. The microservice supply and marketing data is shown in Table 1, which mainly includes customer ordering information:

[0087] Table 1 Microservice supply and marketing data

[0088] Customer Name Service Logo Customer A Composite Service 1 Customer B Composite Service 2 Customer C Composite Service 3 …… ……

[0089] Generally, the orchestration data of the service can be collected from the orchestrator, and the service flow can also contain other service flows, as shown in Table 2 and Table 3: Table 2 indicates that some services are service flows composed of other services in sequence; Table 3 indicates the services included in the service flow.

[0090] Table 2 Microservice orchestration data - correspondence between services and flows

[0091] Service Logo Flow ID Composite Service 1 Stream 1 Composite Service 2 Stream 2 Composite Service 3 Stream 3 …… ……

[0092] Table 3 Microservice orchestration data - correspondence between services and flows

[0093]

[0094] The performance data of each specific service is collected, as shown in Table 4:

[0095] Table 4 Performance data collected

[0096] Service Logo Statistics start time Statistics end time Number of calls Number of successful calls Average call delay (seconds) …… …… …… …… …… …… Basic Service 2 20190425 1600 20190425 1605 100 80 3 …… …… …… …… …… ……

[0097] Collect the fault data of each specific service, as shown in Table 5:

[0098] Table 5 Fault data collected

[0099] Service Logo Time of occurrence Fault Title Fault text Basic Service 3 20190425 1602 Process hang …… …… …… …… ……

[0100] The call success rate threshold and call delay threshold of each specific service can be set based on experience; the set value can be adjusted according to actual conditions to achieve the best effect.

[0101] For example, the call success rate threshold of basic service 2 may be set to 90%; and the call delay threshold may be set to 5 seconds.

[0102] When (number of successful calls / number of calls) of a specific service in Table 4 < call success rate threshold or average call delay < call delay threshold, corresponding fault information is generated. The fault information may include service name, occurrence time, fault title, fault text and other information.

[0103] In Table 4, the call success rate threshold of basic service 2 from 20190425-1600 to 20190425-1605 is 80 / 100=80%<90%, so new fault data is generated as shown in Table 6.

[0104] Table 6 Newly generated fault data

[0105] Service Logo Time of occurrence Fault Title Fault text Basic Service 3 20190425-1605 Call failed …… …… …… …… ……

[0106] When new Table 5 data is received or new Table 6 data is generated, the fault data is analyzed:

[0107] 1) Use the service ID to find the flow ID to which the service belongs from Table 3;

[0108] The above service identifiers are: basic service 2, basic service 3. Then, using "basic service 2" to find the corresponding flow identifiers from Table 3 is: flow 1, flow 2; using "basic service 3" to find the corresponding flow identifier from Table 3 is: flow 1.

[0109] In summary, the flow identifiers that can be found are: flow 1, flow 2.

[0110] 2) Use the flow ID to find the service ID corresponding to the flow from Table 2;

[0111] Use "flow 1" to find out from Table 2 that the service identifier corresponding to the flow is: composite service 1; use "flow 2" to find out from Table 2 that the service identifier corresponding to the flow is: composite service 2.

[0112] 3) Use the new service ID to find the name of the customer who ordered it from Table 1;

[0113] Use "Composite Service 1" to find the customer name that ordered it from Table 1: Customer A

[0114] Use "Composite Service 2" to find the name of the customer who ordered it from Table 1: Customer B.

[0115] 4) Use the new service ID to find the corresponding flow ID from Table 3;

[0116] Use "Composite Service 1" to find the flow ID from Table 3: Flow 3

[0117] Use "flow 3" to find the service ID corresponding to the flow from Table 2: Composite service 3

[0118] Use "Composite Service 3" to find the name of the customer who ordered it from Table 1: Customer C.

[0119] From now on, I can no longer find the new flow ID or the new customer name.

[0120] 5) Output to external parties the specific customers affected by the service failure: Customer A, Customer B, Customer C.

[0121] In summary, this method can clearly, concisely and quickly locate the customer scope affected by microservices without the need for complex microservice topology relationships.

[0122] The present invention also discloses a microservice management device. First, a fifth embodiment of the present invention is given. Figure 4 As shown, it is used to illustrate the structural features of the device.

[0123] The device includes:

[0124] The microservice resource management unit 1 is used to obtain and manage microservice resource management data, wherein the microservice resource management data includes microservice supply and marketing data and microservice orchestration data.

[0125] The microservice supply and marketing data includes microservice provider information and microservice orderer information.

[0126] The microservice orchestration data includes service information and service flow information provided by the microservice.

[0127] The data collection unit 2 is used to obtain the performance data and fault data of each microservice.

[0128] The performance data of each microservice includes the call time, call latency, number of calls, and number of successful calls of the microservice.

[0129] The fault data of each microservice includes the time when the microservice fault occurred and the fault content.

[0130] The fault information generating unit 3 is used to generate corresponding fault information of each microservice according to a preset microservice call threshold and in combination with the performance data and fault data of each microservice collected by the data collecting unit.

[0131] The impact analysis unit 4 is used to determine the impact scope of each microservice fault information based on the microservice fault information generated by the fault information generation unit and the fault data collected by the data collection unit in combination with the microservice resource management data acquired by the microservice resource management unit.

[0132] In order to better illustrate the structure and working mode of each part of the device, the sixth embodiment of the present invention is given. Figure 5 shown.

[0133] Specifically, the microservice resource management unit 1 further includes:

[0134] The microservice supply and marketing data management module 11 is used to obtain and manage the microservice provider information and microservice orderer information contained in the microservice supply and marketing data.

[0135] The microservice orchestration data management module 12 is used to obtain and manage the service information and service flow information provided by the microservices contained in the microservice orchestration data.

[0136] The data acquisition unit 2 further comprises:

[0137] The performance data collection module 21 is used to collect the call time, call delay, call number, and call success number of each microservice.

[0138] The fault data collection module 22 is used to collect the fault occurrence time and fault content of each microservice.

[0139] The fault information generating unit 3 further comprises:

[0140] The threshold setting module 31 is used to preset a microservice call success rate threshold and a call delay threshold.

[0141] The calculation module 32 is used to obtain the average call delay of the microservice according to the call time and call delay of the microservice, and obtain the call success rate of the microservice according to the number of calls and the number of successful calls of the microservice.

[0142] The fault information generating module 33 is used to generate microservice fault information according to the microservice call time in combination with the microservice orchestration data when the microservice call success rate or call delay calculated by the calculating module exceeds the microservice call success rate threshold and call delay threshold set by the threshold setting module.

[0143] The impact analysis unit 4 further comprises:

[0144] The service flow information acquisition module 41 is used to acquire the service flow information in the microservice orchestration data according to the microservice fault information generated by the fault information generation module and the fault data collected by the data collection unit.

[0145] The service information acquisition module 42 is used to acquire the service information provided by the microservice according to the service flow information acquired by the service flow information acquisition module.

[0146] The ordering information acquisition module 43 acquires the microservice ordering party information according to the service information provided by the microservice acquired by the service information acquisition module.

[0147] The impact range determination module 44 is used to determine the impact range of the microservice fault information according to the microservice ordering party information obtained by the ordering information obtaining module.

[0148] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the corresponding processes in the above-described device embodiments can refer to the specific working processes of the aforementioned methods, which will not be repeated here.

[0149] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0150] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein can be implemented directly with hardware, a software module executed by a processor, or a combination of the two. The software module can be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the technical field. The terms "first", "second", "third", "fourth", etc. (if present) in the specification and claims and the above-mentioned drawings are used to distinguish similar parts, and do not have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described here can be implemented in a sequence other than that illustrated here.

[0151] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A microservice management method, characterized in that: The method comprises: Acquire microservice resource management data, wherein the microservice resource management data includes microservice supply and marketing data and microservice orchestration data; the microservice supply and marketing data includes microservice provider information and microservice subscriber information; The provider information includes the provider name and service identifier, the orderer information includes the ordering customer name and the ordering service identifier; the microservice orchestration data includes the correspondence between the service identifier and the service flow identifier; Obtain performance data and fault data for each microservice; According to the preset microservice call threshold, combined with the performance data and fault data of each microservice, corresponding fault information of each microservice is generated; Determine the impact scope of each microservice fault information according to the microservice fault information combined with the resource management data of the microservice, and the method is specifically as follows: Acquire service flow information in the microservice orchestration data according to the microservice fault information; Acquire service information provided by the microservice according to the service flow information; Acquire the microservice subscriber information according to the service information provided by the microservice; The microservice ordering party information is determined to be an impact scope of the microservice fault information.

2. The method according to claim 1, characterized in that: The microservice orchestration data includes service information and service flow information provided by the microservice.

3. The method according to claim 2, characterized in that: The performance data of each microservice includes the call time, call delay, number of calls, and number of successful calls of the microservice; The fault data of each microservice includes the time when the microservice fault occurred and the fault content.

4. The method according to claim 3, characterized in that The method for generating corresponding fault information of each microservice according to the preset microservice call threshold and combining the performance data and fault data of each microservice is specifically as follows: Preset microservice call success rate threshold and call delay threshold; Obtain an average call delay of the microservice according to the call time and call delay of the microservice, and obtain a call success rate of the microservice according to the number of calls and the number of successful calls of the microservice; When the microservice call success rate or call delay exceeds the microservice call success rate threshold and the call delay threshold, microservice fault information is generated according to the microservice call time in combination with the microservice orchestration data.

5. A microservice management device, characterized in that: The device comprises: A microservice resource management unit, used to obtain and manage microservice resource management data, wherein the microservice resource management data includes microservice supply and marketing data and microservice orchestration data; the microservice supply and marketing data includes microservice provider information and microservice orderer information; The provider information includes the provider name and service identifier, the orderer information includes the ordering customer name and the ordering service identifier; the microservice orchestration data includes the correspondence between the service identifier and the service flow identifier; Data collection unit, used to obtain performance data and fault data of each microservice; A fault information generating unit, configured to generate corresponding fault information of each microservice according to a preset microservice call threshold value and in combination with the performance data and fault data of each microservice collected by the data collecting unit; The impact analysis unit is used to determine the impact scope of each microservice fault information according to the microservice fault information generated by the fault information generation unit and the fault data collected by the data collection unit in combination with the microservice resource management data obtained by the microservice resource management unit, and the method is specifically as follows: Acquire service flow information in the microservice orchestration data according to the microservice fault information; Acquire service information provided by the microservice according to the service flow information; Acquire the microservice subscriber information according to the service information provided by the microservice; The microservice ordering party information is determined to be an impact scope of the microservice fault information.

6. The device according to claim 5, characterized in that The microservice resource management unit further includes: A microservice supply and marketing data management module is used to obtain and manage the microservice provider information and microservice subscriber information contained in the microservice supply and marketing data; the provider information includes the provider name and service ID, and the subscriber information includes the subscribed customer name and the subscribed service ID; The microservice orchestration data management module is used to obtain and manage the service information and service flow information provided by the microservices contained in the microservice orchestration data.

7. The device according to claim 6, characterized in that The data acquisition unit further comprises: A performance data collection module is used to collect the call time, call delay, number of calls, and number of successful calls of each microservice; The fault data collection module is used to collect the fault occurrence time and fault content of each microservice.

8. The device according to claim 7, characterized in that: The fault information generating unit further comprises: Threshold setting module, used to preset microservice call success rate threshold and call delay threshold; A calculation module is used to obtain an average call delay of the microservice according to the call time and call delay of the microservice, and obtain a call success rate of the microservice according to the number of calls and the number of successful calls of the microservice; The fault information generating module is used to generate microservice fault information according to the microservice call time in combination with the microservice orchestration data when the microservice call success rate or call delay calculated by the calculating module exceeds the microservice call success rate threshold and call delay threshold set by the threshold setting module.

9. The device according to claim 8, characterized in that The impact analysis unit further comprises: A service flow information acquisition module, configured to acquire service flow information in the microservice orchestration data according to the microservice fault information generated by the fault information generation module and the fault data collected by the data collection unit; A service information acquisition module, used to acquire service information provided by the microservice according to the service flow information acquired by the service flow information acquisition module; An ordering information acquisition module, which acquires the microservice ordering party information according to the service information provided by the microservice acquired by the service information acquisition module; The impact scope determination module is used to determine the impact scope of the microservice fault information according to the microservice ordering party information obtained by the ordering information acquisition module.

Images