Fusing method and device for service exception, electronic equipment and medium

Abstract

The invention provides a service exception fusing method and device, electronic equipment and a medium, and relates to the technical field of communication. In the business operation process, if a service request of a certain city is abnormal and meets a fusing condition, a server subsequently receives an SaaS service request of the current city, directly refuses to process the corresponding SaaS service request and returns an error exception, so that the service exception can be effectively prevented from being processed. And after the fusing duration is reached, new SaaS service request entry of the corresponding city is recovered again, and business processing is recovered. According to the method and the device, the abnormal city can be independently fused, so that the purpose of protecting the whole service link is achieved; through independent processing of single city service, other cities are ensured not to be influenced, so that the whole service link business can be ensured to be normally carried out.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, electronic device and medium for fusing abnormal services. Background Art

[0002] In the SaaS (Software as a Service) model, when a city's service encounters sudden traffic, unstable operation, or slow response, the entire service chain may collapse. This not only affects the city where the problem occurs, but also affects users in other cities, causing business interruptions. Existing technologies can only handle normal request traffic, and there is no effective prevention and recovery mechanism for such abnormal situations. Summary of the invention

[0003] The purpose of the embodiments of the present application is to provide a service exception fuse method, device, electronic device and medium, which are used to solve the above-mentioned problems existing in the prior art, and can solve the problem of single city exception causing global failure faced by traditional SaaS platforms, thereby significantly improving user experience and service quality.

[0004] In a first aspect, a method for fusing service anomalies is provided, the method being applied to a service management system for managing multiple cities, and the method may include:

[0005] Obtaining SaaS service requests from each city; the SaaS service requests include service request information;

[0006] For any city, check whether the service request information obtained meets the fuse conditions;

[0007] If so, the service interface that sends the SaaS service request in the corresponding city is fused based on the obtained target fusion duration.

[0008] In a possible implementation, the service request information includes: a total number of requests;

[0009] Whether the service request information meets the fuse conditions, including:

[0010] Whether the total number of requests reaches a configured first threshold within a preset time period.

[0011] In a possible implementation, whether the number of requests within a preset time period reaches a configured second threshold; wherein the number of requests is determined based on the number of request call durations of each SaaS service request exceeding the configured duration threshold.

[0012] In a possible implementation, the service request information includes: the total number of requests and the request call duration of each SaaS service request;

[0013] Whether the service request information meets the fuse conditions, including:

[0014] Whether the total number of requests reaches a configured first threshold and the target ratio reaches a configured third threshold within a preset time period;

[0015] The process of determining the target ratio includes: determining the number of requests for which the request call duration of each SaaS service request exceeds a configured duration threshold;

[0016] The request quantity and the total request quantity are calculated to obtain the target ratio.

[0017] In a possible implementation, the process of obtaining the target fuse duration includes:

[0018] Based on the correspondence between different configured target ratios and different fuse durations, determine the target fuse duration corresponding to the target ratio;

[0019] During the target fuse duration, the total number of requests and the target ratio are detected at the configured time interval. If the total number of requests does not reach the configured first threshold and the target ratio does not reach the configured third threshold, the service interface for sending SaaS service requests to the city is restored.

[0020] In a possible implementation, a configuration rule of the fuse duration is: every time the target ratio increases by a preset proportion, the fuse duration increases by a preset duration.

[0021] In a possible implementation, the configuration rule of the fuse duration is:

[0022] Based on a preset circuit breaker algorithm, configure the circuit breaker duration;

[0023] The fuse algorithm is:

[0024] T=min(max(T min , S×R×L), T max )

[0025] Among them, T is the fuse duration, S is the failure severity, R is the recovery coefficient, L is the load factor, T min is the preset minimum fuse duration, T max The preset maximum fuse duration.

[0026] In a second aspect, a service abnormality fuse device is provided, which is applied to a service management system for managing multiple cities, and the device may include:

[0027] An acquisition unit, used to acquire SaaS service requests from each city; the SaaS service request includes service request information;

[0028] A detection unit, used for detecting whether the obtained service request information meets the fuse condition for any city;

[0029] The circuit breaker unit is used to, if so, fuse the service interface that sends the SaaS service request in the corresponding city based on the obtained target circuit breaker duration.

[0030] In a third aspect, an electronic device is provided, the electronic device comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0031] Memory, used to store computer programs;

[0032] The processor is used to implement any method step described in the first aspect when executing the program stored in the memory.

[0033] In a fourth aspect, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any method step described in the first aspect is implemented.

[0034] The present application provides a method for fusing service exceptions, the method comprising: obtaining SaaS service requests from various cities; the SaaS service requests include service request information; for any city, detecting whether the obtained service request information meets the fusing conditions; if so, based on the obtained target fusing duration, fusing the service interface that sends the SaaS service request from the corresponding city. During the business operation of the present application, if the service request of a certain city is abnormal and meets the fusing conditions, then the server will subsequently receive a SaaS service request from the current city, directly refuse to process the corresponding SaaS service request and return an error exception, and after the fusing duration is reached, resume the entry of new SaaS service requests from the corresponding city and resume business processing. The present application can perform separate fusing processing for abnormal cities to achieve the purpose of protecting the entire service link; by separately processing the services of a single city, it ensures that the remaining cities are not affected, thereby ensuring that the overall service link business can proceed normally. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0036] Figure 1A system architecture diagram of a fuse method applied to service exceptions provided in an embodiment of the present application;

[0037] Figure 2 A flow chart of a method for fusing a service exception provided in an embodiment of the present application;

[0038] Figure 3 A schematic diagram of the structure of a fuse device for abnormal service provided in an embodiment of the present application;

[0039] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0041] The service abnormality fuse method provided in the embodiment of the present application can be applied to Figure 1 In the system architecture shown in Figure 1 As shown, the system may include: a service management system and a server. The server may be a physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0042] In the SaaS (Software as a Service) model, when a city's service encounters sudden traffic, unstable operation, or slow response, the entire service chain may collapse. This not only affects the city where the problem occurs, but also affects users in other cities, causing business interruptions. Existing technologies can only handle normal request traffic, and there is no effective prevention and recovery mechanism for such abnormal situations.

[0043] That is to say, the prior art has the following problems:

[0044] ① The service in a certain city becomes abnormal, causing the entire service chain to collapse and the business in other cities to be unable to proceed normally.

[0045] ② The concurrent service volume of a certain city increases suddenly, and there is no emergency solution. The abnormal service will affect the business of other cities, and the business of other cities will not be able to continue normally.

[0046] ③After the service crashes, there is no corresponding recovery mechanism and the business cannot be restored quickly.

[0047] Therefore, the present application provides a service exception fuse method, device, electronic device and medium to solve the above-mentioned problems existing in the prior art, and can solve the problem of single city exceptions causing global failures faced by traditional SaaS platforms, thereby significantly improving user experience and service quality.

[0048] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

[0049] Figure 2 A flow chart of a method for fusing a service exception provided in an embodiment of the present application. Figure 2 As shown, the method may include:

[0050] Step S210: Obtain SaaS service requests from each city.

[0051] The SaaS service request includes service request information;

[0052] Specifically, since the service management system manages SaaS service requests of multiple cities, corresponding service interfaces exist in each of the multiple cities managed by the system.

[0053] The SaaS service requests of each city reach the service management system through the corresponding service interface.

[0054] It is understandable that the SaaS service request of each city may be one or more. The SaaS service request may be a purchase order request, a bus card recharge request, or a vehicle Bluetooth key addition / deletion / modification request, etc.

[0055] Step S220: Detect whether the acquired service request information meets the fuse condition, and determine the status of the corresponding service interface according to the detection result.

[0056] A. Service request information includes: total number of requests;

[0057] For the service interface corresponding to any city, check whether the service request information of the service interface of the city meets the fuse condition, which can be:

[0058] Detecting whether the total number of requests reaches a configured first threshold within a preset time period;

[0059] If the detection result is yes, the service interface that sends the SaaS service request to the city will be fused based on the obtained target fusion duration;

[0060] If the detection result is no, it indicates that the total number of SaaS service requests received by the service interface of the city within the preset time period is normal, and there is no need to process the service interface sending SaaS service requests of the city.

[0061] B. Service request information includes: the request call duration of each SaaS service request;

[0062] For the service interface corresponding to any city, check whether the service request information of the service interface of the city meets the fuse condition, which can be:

[0063] Whether the number of requests reaches a configured second threshold within a preset time period;

[0064] The number of requests is determined based on the number of times the request call duration of each SaaS service request exceeds a configured duration threshold.

[0065] If the detection result is yes, the service interface that sends the SaaS service request to the city will be fused based on the obtained target fusion duration;

[0066] If the detection result is no, it means that the number of request call durations of each SaaS service request in the city within the preset time period that exceeds the configured duration threshold does not reach the configured second threshold, that is, the request call duration of each SaaS service request is normal, and there is no need to process the service interface that sends the SaaS service request to the city.

[0067] C. Service request information includes: the total number of requests and the request call duration of each SaaS service request;

[0068] For the service interface corresponding to any city, check whether the service request information of the service interface of the city meets the fuse condition, which can be:

[0069] Whether the total number of requests reaches a configured first threshold and the target ratio reaches a configured third threshold within a preset time period;

[0070] Furthermore, the process of determining the target ratio includes: determining the number of requests for each SaaS service request whose request call duration exceeds a configured duration threshold; and calculating the number of requests and the total number of requests to obtain the target ratio.

[0071] If the detection result is that the total number of requests within the preset time period reaches the configured first threshold and the target ratio reaches the configured third threshold, the service interface that sends the SaaS service request for the city is fused based on the obtained target fusion duration;

[0072] For example: if the total number of SaaS service requests in a city is greater than the first threshold and the target ratio reaches the configured third threshold, the service interface that sends SaaS service requests to the city will be fused based on the obtained target fusion duration; for example: if the total number of requests in a city is more than 5 times and the target ratio is greater than 40% within a continuous 2 minutes, the fusion will be triggered.

[0073] During the fuse period, the service interface corresponding to the city will no longer receive new SaaS service requests, and will only process existing SaaS service requests. When the target ratio drops below 40%, the current city will resume normal business requests. If the total number of requests reaches the configured first threshold and / or the target ratio reaches the configured third threshold after the fuse period reaches the specified time, the service interface corresponding to the city will remain in the fuse state.

[0074] If the detection result is that the total number of requests within the preset time period does not reach the configured first threshold and the target ratio does not reach the configured third threshold, it indicates that the reception and processing process of each SaaS service request within the preset time period is normal, and there is no need to process the service interface that sends the SaaS service request to the city.

[0075] In some embodiments, the process of acquiring the target blowing duration includes: as shown in Table 1, based on the correspondence between different configured target ratios and different blowing durations, determining the target blowing duration corresponding to the target ratio.

[0076] Table 1

[0077]

[0078]

[0079] Afterwards, during the target circuit breaking duration, the total number of requests and the target ratio are checked at the configured time interval. If the total number of requests does not reach the configured first threshold and the target ratio does not reach the configured third threshold, the service interface for sending SaaS service requests to the city will be restored; otherwise, the service interface will continue to remain circuit-broken.

[0080] The configuration rule for the corresponding relationship between different target ratios and different fuse durations is: for every increase in the target ratio by a preset percentage, the fuse duration increases by a preset duration. For example, for every 10% increase in the target ratio, the corresponding fuse duration range increases by 30 seconds. When the target ratio reaches 100%, the fuse duration of the current city reaches the maximum duration range of 1 to 240 seconds.

[0081] In another embodiment, the configuration rule of the fuse duration is: based on a preset fuse algorithm, configure the fuse duration;

[0082] The fuse algorithm can be:

[0083] T=min(max(T min , S×R×L), T max )

[0084] Among them, T is the target fuse duration, S is the failure severity, R is the recovery coefficient, L is the load factor, and T min is the preset minimum fuse duration, T max The preset maximum fuse duration.

[0085] Furthermore, S×R×L as a whole is a process of adjusting the target fusing duration by combining the failure severity, the recovery coefficient and the load factor (current load condition).

[0086] In actual applications, parameters such as S, R, and L may need to be dynamically adjusted based on real-time monitoring data rather than being fixed.

[0087] In some embodiments, failure severity (S):

[0088] Failure severity can be defined by the type of abnormal service and its impact on user experience or business processes. For example, abnormal service unavailability caused by momentary network fluctuations may be minor, while database connection loss may be severe.

[0089] Quantification method: Different weights can be set according to the abnormal level of abnormal services. For example, a minor error is set to 0.1, a medium error is set to 0.5, and a severe error is set to 1. This can be determined by analyzing the error information in the historical log and its impact range.

[0090] Coefficient of restitution (R):

[0091] The recovery factor reflects the ratio of time required for a service request to recover from a fault state. It can be estimated based on historical data on fault occurrence and recovery time. For service interfaces in some regions, it may take a long time to fully recover, while for other regions, it may be recovered within a few minutes.

[0092] Calculation method: The average recovery time can be divided by a certain benchmark time (such as the shortest recovery time) to obtain a relative value as the recovery coefficient. If there is a lack of historical data, you can start from the experience data of similar regions or base it on expert estimates.

[0093] Load factor(L):

[0094] Definition and measurement: The load factor reflects the current workload of the system and can be measured by indicators such as CPU usage, memory usage, and request processing rate. Under high load conditions, the service interface may take longer to recover or process new requests.

[0095] Quantification method: You can use monitoring tools to obtain real-time service interface performance indicators and convert them into proportional factors relative to normal working conditions. For example, if the current CPU usage is 80% and it is 40% under normal conditions, the load factor can be set to 2 (that is, the current load is twice the normal load).

[0096] In some embodiments, dynamic threshold adjustment: dynamically adjust the fuse threshold (first threshold, second threshold or third threshold) according to the total number of requests for the historical time period and the corresponding historical SaaS service requests. Further, a prediction model is established to predict the peak of the total number of requests that may occur in advance, and take flow limiting measures in advance to avoid service crashes. Specifically, using an adaptive learning algorithm, the service management system can dynamically adjust these fuse thresholds, that is, dynamically set the fuse thresholds according to historical data (such as error rate trends in the past few days or weeks) and real-time traffic changes (such as the current second-level request volume). In this way, the service management system can trigger the fuse in advance when the traffic surges to prevent system overload; and appropriately relax the threshold when the traffic is normal to improve resource utilization. The adaptive learning algorithm can also further enhance the adaptability of the system by building a prediction model. This type of model can analyze traffic data from multiple angles, including but not limited to time series analysis, periodic feature recognition, etc., to predict future traffic trends. Once the prediction model detects an upcoming traffic peak, the system can pre-adjust the fuse strategy, such as reducing the service level of certain non-core functions (such as delaying response time or reducing the number of concurrent processing), so as to reserve enough resources to cope with the upcoming high load. In addition, the prediction model can also be used to identify key factors that may cause service crashes (such as abnormal request patterns within a specific time period) and take preventive measures in advance, such as increasing the monitoring frequency or starting redundant backup services. The adaptive learning algorithm can not only improve the reliability and stability of the service, but also optimize the efficiency of resource utilization while ensuring user experience. This intelligent adaptive learning strategy is suitable for a variety of application scenarios, including but not limited to high-concurrency, high-availability business scenarios such as Internet finance, e-commerce, and social media platforms.

[0097] In some embodiments, considering the difference in request density of SaaS service requests in different geographical areas, a lower fuse threshold is set for high-density areas. Specifically, the managed geographical area is divided into multiple sub-areas, each of which represents a specific city or region. For example, it can be divided by province or city level. Collect historical SaaS service request data of each sub-area, and count the average number of requests and request density of each sub-area. Request density can be defined as the number of requests per unit time in a certain historical time period. Afterwards, the fuse threshold is dynamically adjusted according to the request density of each sub-area. For sub-areas with higher request density, a lower fuse threshold is set to trigger the fuse mechanism earlier; for sub-areas with lower request density, a higher fuse threshold is set. During the operation of the service management system, the request density of each sub-area is monitored in real time, and the fuse threshold is dynamically adjusted according to the actual situation. For example, if the request density of a certain area suddenly increases, the fuse threshold of the area can be immediately reduced to avoid service overload. In this way, the fuse threshold is dynamically adjusted according to the request density of different areas, which can more effectively deal with abnormal traffic conditions in different regions. This method not only improves the robustness and stability of the system, but also better guarantees the service quality of each region and improves user experience.

[0098] The present application provides a method for fusing service exceptions, the method comprising: obtaining SaaS service requests from various cities; the SaaS service request includes service request information; for any city, detecting whether the obtained service request information meets the fusing conditions; if so, based on the obtained target fusing duration, fusing the service interface that sends the SaaS service request from the corresponding city. The present application performs separate fusing processing for abnormal cities during business operations, thereby achieving the purpose of protecting the entire service link. During business operations, if the service request of a certain city is abnormal and meets the fusing conditions, the server will subsequently receive a SaaS service request from the current city, directly refuse to process the corresponding SaaS service request and return an error exception. After the fusing duration is reached, the new SaaS service request of the corresponding city is restored to enter again, and business processing is resumed. By separately processing the services of a single city, it is ensured that the remaining cities are not affected, the business proceeds normally, and the business of the entire service link can proceed normally.

[0099] Corresponding to the above method, the embodiment of the present application also provides a service abnormality fuse device, such as Figure 3 As shown, the device comprises:

[0100] An acquisition unit 310 is used to acquire SaaS service requests of each city; the SaaS service request includes service request information;

[0101] A detection unit 320, configured to detect, for any city, whether the obtained service request information satisfies a fuse condition;

[0102] The fuse unit 330 is used to, if yes, fuse the service interface that sends the SaaS service request in the corresponding city based on the obtained target fuse duration.

[0103] The functions of each functional unit of a service abnormality fuse device provided in the above-mentioned embodiment of the present application can be realized through the above-mentioned method steps. Therefore, the specific working process and beneficial effects of each unit in a service abnormality fuse device provided in the embodiment of the present application are not repeated here.

[0104] The present application also provides an electronic device, such as Figure 4 As shown, it includes a processor 410 , a communication interface 420 , a memory 430 and a communication bus 440 , wherein the processor 410 , the communication interface 420 , and the memory 430 communicate with each other via the communication bus 440 .

[0105] Memory 430, for storing computer programs;

[0106] The processor 410 is used to execute the program stored in the memory 430 to implement the following steps:

[0107] Obtaining SaaS service requests from each city; the SaaS service requests include service request information;

[0108] For any city, check whether the service request information obtained meets the fuse conditions;

[0109] If so, the service interface that sends the SaaS service request in the corresponding city is fused based on the obtained target fusion duration.

[0110] The communication bus mentioned above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0111] The communication interface is used for communication between the above electronic device and other devices.

[0112] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0113] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0114] The implementation methods and beneficial effects of the components of the electronic device in the above embodiments to solve the problems can be seen in Figure 2 The various steps in the illustrated embodiment are implemented, therefore, the specific working process and beneficial effects of the electronic device provided by the embodiment of the present application are not repeated here.

[0115] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which instructions are stored. When the computer-readable storage medium is executed on a computer, the computer executes a method for breaking a service exception as described in any one of the above embodiments.

[0116] In another embodiment provided by the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute a method for breaking a service exception as described in any one of the above embodiments.

[0117] Those skilled in the art will appreciate that the embodiments in the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt a complete hardware embodiment, a complete software embodiment, or a form of an embodiment combining software and hardware. Moreover, the present application may adopt a form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0118] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0119] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0120] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0121] Unless otherwise defined, the technical terms or scientific terms used in this application should be understood by people with ordinary skills in the field to which the present invention belongs. "First", "second" and similar words used in this application do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprise" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect", "couple" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0122] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they are aware of the basic creative concepts. Therefore, the present application embodiments are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application embodiments.

[0123] Obviously, those skilled in the art can make various changes and modifications to the embodiments in the present application without departing from the spirit and scope of the embodiments in the present application. Thus, if these modifications and variations of the embodiments in the present application are within the scope of the embodiments in the present application and their equivalents, the embodiments in the present application are also intended to include these modifications and variations.

Claims

1. A method for fusing service exceptions, characterized in that: The method is applied to a service management system for managing multiple cities, and the method comprises: Obtaining SaaS service requests from each city; the SaaS service requests include service request information; For any city, check whether the service request information obtained meets the fuse conditions; If so, the service interface that sends the SaaS service request in the corresponding city is fused based on the obtained target fusion duration.

2. The method according to claim 1, characterized in that The service request information includes: the total number of requests; Whether the service request information meets the fuse conditions, including: Whether the total number of requests reaches a configured first threshold within a preset time period.

3. The method according to claim 2, characterized in that The service request information includes: the request call duration of each SaaS service request; Whether the service request information meets the fuse conditions, including: Whether the number of requests reaches a configured second threshold within a preset time period; wherein the number of requests is determined based on the number of times the request call duration of each SaaS service request exceeds the configured duration threshold.

4. The method according to claim 1, characterized in that The service request information includes: the total number of requests and the request call duration of each SaaS service request; Whether the service request information meets the fuse conditions, including: Whether the total number of requests reaches a configured first threshold and the target ratio reaches a configured third threshold within a preset time period; The process of determining the target ratio includes: determining the number of requests for which the request call duration of each SaaS service request exceeds a configured duration threshold; The request quantity and the total request quantity are calculated to obtain the target ratio.

5. The method according to claim 4, characterized in that The process of obtaining the target fuse duration includes: Based on the correspondence between different configured target ratios and different fuse durations, determine the target fuse duration corresponding to the target ratio; During the target fuse duration, the total number of requests and the target ratio are detected at the configured time interval. If the total number of requests does not reach the configured first threshold and the target ratio does not reach the configured third threshold, the service interface for sending SaaS service requests to the city is restored.

6. The method according to claim 5, characterized in that The configuration rule of the fuse duration is: every time the target ratio increases by a preset proportion, the fuse duration increases by a preset duration.

7. The method according to claim 5, characterized in that The configuration rules for the fuse duration are: Based on a preset circuit breaker algorithm, configure the circuit breaker duration; The fuse algorithm is: T=min(max(T min ,S×R×L),T max ) Among them, T is the fuse duration, S is the failure severity, R is the recovery coefficient, L is the load factor, T min is the preset minimum fuse duration, T max The preset maximum fuse duration.

8. A service abnormality fuse device, characterized in that: The device is applied to a service management system for managing multiple cities, and the device comprises: An acquisition unit, used to acquire SaaS service requests from each city; the SaaS service requests include service request information; A detection unit, used for detecting whether the obtained service request information meets the fuse condition for any city; The circuit breaker unit is used to, if so, fuse the service interface that sends the SaaS service request in the corresponding city based on the obtained target circuit breaker duration.

9. An electronic device, characterized in that: The electronic device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory, used to store computer programs; A processor, for implementing the method steps described in any one of claims 1 to 7 when executing a program stored in a memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 1 to 7 are implemented.

Images