System current limiting method and device, computer equipment and storage medium

Abstract

The invention discloses a system flow limiting method and device, computer equipment and a storage medium, and relates to the technical field of data processing.The method comprises the steps that resource consumption information of all service systems in a current target system is collected, and calling relation information between all the service systems is obtained through analysis; based on the resource consumption information and the calling relation information, judging whether the target system needs to start current limiting or not; when the target system needs to start current limiting, generating a current limiting strategy of a seat dimension according to the output value information of the seat of the target system; and carrying out current limiting processing on the target system based on the current limiting strategy. According to the method provided by the invention, the target system can be subjected to flow limiting processing according to the flow limiting strategy of the seat dimension, so that the completeness of the seat business process in the target system can be effectively ensured.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a system current limiting method, device, computer equipment and non-volatile computer-readable storage medium. Background Art

[0002] At present, with the rapid development of Internet technology, the number of requests for online services and applications is increasing, which puts higher requirements on the stability and availability of the system. In order to ensure the stable operation of the system under high concurrency, current limiting and degradation strategies have become indispensable technical means. At present, current limiting technology is mainly implemented through algorithms such as sliding windows and leaky buckets, while degradation strategies rely on frameworks such as Sentinel for request-level control. These technologies can effectively ensure the availability of the system in simple business scenarios, but they have the following disadvantages when dealing with complex business processes:

[0003] 1. Consistency issues in the interaction of multiple business systems in the system: In complex business scenarios, such as the sales of auto insurance or non-auto insurance services, agent operations often require request interactions with multiple business systems. For example, a business process may need to go through business system A, business system B, and business system C in sequence. If the requests of the first two business systems A and B are processed normally, but the request of the last business system C is limited or downgraded, the entire business process will fail and the agent will need to reprocess the business, which not only increases the workload but also affects the user experience.

[0004] 2. Risk of business process interruption: When agents are completing business, they may need to interact with the system multiple times and complete multiple steps. The existing flow control and downgrade strategies may cause agents to encounter flow control in subsequent links after completing the previous steps, resulting in business process interruption. In this case, the business is not completed for the agents, which not only increases the workload of the agents, but also may cause data inconsistency problems.

[0005] 3. Lack of dynamic adjustment capabilities: Existing throttling and degradation strategies often lack an in-depth understanding of business processes and dynamic adjustment capabilities. When faced with different business scenarios and request characteristics, fixed throttling rules may not be able to respond flexibly, resulting in unreasonable resource allocation and affecting the overall performance of the system.

[0006] Based on this, how to provide a system current limiting method, device, computer equipment and non-volatile computer-readable storage medium that can effectively ensure the integrity of the agent business process in the target system is a problem that urgently needs to be solved by technical personnel in this field. Summary of the invention

[0007] In view of the above-mentioned shortcomings of the prior art, the purpose of the present invention is to provide a system current limiting method, device, computer equipment and non-volatile computer-readable storage medium that can be used in financial technology or other related fields, aiming to solve the problem of how to effectively ensure the integrity of the agent business process in the target system.

[0008] In order to achieve the above object, the present invention adopts the following technical solutions:

[0009] A system current limiting method, comprising:

[0010] Collect resource consumption information of each business system in the current target system, and analyze and obtain the call relationship information between each of the business systems;

[0011] Based on the resource consumption information and the call relationship information, determining whether the target system needs to start current limiting;

[0012] When the target system needs to start flow limiting, a flow limiting strategy in the seat dimension is generated according to the output value information of the seats of the target system;

[0013] Based on the current limiting strategy, current limiting processing is performed on the target system.

[0014] In a further technical solution, the system flow limiting method, wherein when the target system needs to start flow limiting, a flow limiting strategy in the seat dimension is generated according to the output value information of the seat of the target system, including:

[0015] When the target system needs to start current limiting, the output value information of the agent is measured using the random forest algorithm based on the agent portrait, customer portrait and corresponding recommended sales product information of the target system;

[0016] According to the output value information and the preset pressure value that the target system can bear, a corresponding maximum output value is calculated using a dynamic programming algorithm;

[0017] Based on the maximum output value, a flow limiting strategy for the target system seat dimension is generated.

[0018] In a further technical solution, the system current limiting method, wherein the current limiting process is performed on the target system based on the current limiting strategy, comprises:

[0019] Sending the current limiting strategy to the gateways of each of the business systems related to the call link in the target system;

[0020] The gateway of each of the business systems releases agent requests that comply with the current limiting strategy to the corresponding business system for processing.

[0021] In a further technical solution, the system current limiting method, wherein after the current limiting process is performed on the target system based on the current limiting strategy, further comprises:

[0022] A scheduled task is used to regularly update the current limiting strategy and send it to the target system for execution.

[0023] In a further technical solution, the system current limiting method, wherein the resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained by analysis, wherein:

[0024] The resource consumption information includes CPU usage, memory usage, QPS, interface processing time, and interface error information.

[0025] In a further technical solution, the system current limiting method, wherein the resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained by analysis, wherein:

[0026] The call relationship information includes call links, call frequencies, call delays, and call errors.

[0027] A system current limiting device, comprising:

[0028] The collection and analysis module is used to collect resource consumption information of each business system in the current target system, and analyze and obtain the call relationship information between each of the business systems;

[0029] A judgment module, used for judging whether the target system needs to start current limiting based on the resource consumption information and the call relationship information;

[0030] A strategy generation module, used for generating a flow limiting strategy in the seat dimension according to the output value information of the seats of the target system when the target system needs to start flow limiting;

[0031] The current limiting module is used to perform current limiting processing on the target system based on the current limiting strategy.

[0032] In a further technical solution, the system current limiting device further comprises:

[0033] The timing update module is used to adopt a timing task to regularly update the current limiting strategy and send it to the target system for execution.

[0034] A computer device, wherein the computer device comprises at least one processor; and

[0035] a memory communicatively connected to the at least one processor; wherein,

[0036] The memory stores a computer program that can be executed by the at least one processor. When the computer program is executed by the at least one processor, the system current limiting method as described in any one of the above items can be implemented.

[0037] A non-volatile computer-readable storage medium stores a computer program, wherein the computer program, when executed by at least one processor, can implement any of the system current limiting methods described above.

[0038] Compared with the prior art, the present invention provides a system current limiting method, apparatus, computer equipment and non-volatile computer-readable storage medium, wherein the method includes: collecting resource consumption information of each business system in the current target system, and analyzing to obtain the call relationship information between each business system; judging whether the target system needs to start current limiting based on the resource consumption information and the call relationship information; when the target system needs to start current limiting, generating a current limiting strategy in the seat dimension according to the output value information of the seat of the target system; and implementing current limiting processing on the target system based on the current limiting strategy. In this way, the method of the present invention can realize current limiting processing on the target system according to the current limiting strategy in the seat dimension, thereby effectively ensuring the integrity of the seat business process in the target system. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] 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 recorded in the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0040] Figure 1 A schematic flow chart of a system current limiting method provided in an embodiment of the present invention.

[0041] Figure 2 Another schematic diagram of a flow chart of a system current limiting method provided by an embodiment of the present invention.

[0042] Figure 3 A schematic diagram of functional modules of a system current limiting device provided in an embodiment of the present invention.

[0043] Figure 4 A schematic diagram of another functional module of a system current limiting device provided in an embodiment of the present invention.

[0044] Figure 5 A schematic diagram of the hardware structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and effect of the present invention clearer and more specific, the present invention is further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0046] In the description of the present invention, the terms "include", "including", "have", "contain", etc. are all open terms, which mean including but not limited to. The descriptions with reference to the terms "one embodiment", "a specific embodiment", "some embodiments", "for example", etc. mean that the specific features, structures or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures or characteristics described may be combined in a suitable manner in any one or more embodiments or examples. The order of steps involved in each embodiment is used to schematically illustrate the implementation of the present application, and the order of steps therein is not limited and can be appropriately adjusted as needed.

[0047] Various non-limiting embodiments of the present invention are described in detail below in conjunction with the accompanying drawings.

[0048] At present, with the rapid development of Internet technology, the number of requests for online services and applications is increasing, which puts higher requirements on the stability and availability of the system. In order to ensure the stable operation of the system under high concurrency, current limiting and degradation strategies have become indispensable technical means. At present, current limiting technology is mainly implemented through algorithms such as sliding windows and leaky buckets, while degradation strategies rely on frameworks such as Sentinel for request-level control. These technologies can effectively ensure the availability of the system in simple business scenarios, but they have the following disadvantages when dealing with complex business processes:

[0049] 1. Consistency issues in the interaction of multiple business systems in the system: In complex business scenarios, such as the sales of auto insurance or non-auto insurance services, agent operations often require request interactions with multiple business systems. For example, a business process may need to go through business system A, business system B, and business system C in sequence. If the requests of the first two business systems A and B are processed normally, but the request of the last business system C is limited or downgraded, the entire business process will fail and the agent will need to reprocess the business, which not only increases the workload but also affects the user experience.

[0050] 2. Risk of business process interruption: When agents are completing business, they may need to interact with the system multiple times and complete multiple steps. The existing flow control and downgrade strategies may cause agents to encounter flow control in subsequent links after completing the previous steps, resulting in business process interruption. In this case, the business is not completed for the agents, which not only increases the workload of the agents, but also may cause data inconsistency problems.

[0051] 3. Lack of dynamic adjustment capabilities: Existing throttling and degradation strategies often lack an in-depth understanding of business processes and dynamic adjustment capabilities. When faced with different business scenarios and request characteristics, fixed throttling rules may not be able to respond flexibly, resulting in unreasonable resource allocation and affecting the overall performance of the system.

[0052] Based on this, how to provide a system current limiting method, device, computer equipment and non-volatile computer-readable storage medium that can effectively ensure the integrity of the agent business process in the target system is a problem that urgently needs to be solved by technical personnel in this field.

[0053] Therefore, to solve the above problem, please refer to Figure 1 , an embodiment of the present invention provides a system current limiting method, wherein the method comprises the steps of:

[0054] S100, collecting resource consumption information of each business system in the current target system, and analyzing to obtain call relationship information between each of the business systems;

[0055] S200, judging whether the target system needs to start current limiting based on the resource consumption information and the call relationship information;

[0056] S300: When the target system needs to start flow limiting, a flow limiting strategy in the seat dimension is generated according to the output value information of the seats of the target system;

[0057] S400: Based on the current limiting strategy, current limiting processing is performed on the target system.

[0058] Furthermore, in the system current limiting method, in step S100, resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained through analysis, wherein:

[0059] The resource consumption information includes CPU usage, memory usage, QPS, interface processing time, and interface error information;

[0060] The call relationship information includes call links, call frequencies, call delays, and call errors, etc.

[0061] In the specific implementation, in this embodiment, the resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained by analysis, wherein the specific implementation process is as follows:

[0062] 1) Resource consumption information collection

[0063] Collect resource consumption information of each business system in the current target system, wherein the resource consumption information includes:

[0064] CPU usage: monitor the CPU load to understand whether the processing capacity of each business system has reached a bottleneck;

[0065] Memory usage: Track memory usage to ensure that each business system has sufficient memory resources to process requests;

[0066] QPS (query rate per second): measures the number of requests that each business system can process per second, and is an important indicator for measuring system throughput;

[0067] Interface processing time: Record the processing time of each interface request in each business system to identify performance bottlenecks;

[0068] Interface error information: collects logs and error information of interface call failures in various business systems to facilitate problem diagnosis and repair;

[0069] 2) Call relationship analysis

[0070] Determine the dependencies and calling sequence between the business systems in the target system, and use tracking tools or log analysis to understand the request flow path between the business systems. The call relationship information between the business systems in the current target system can be obtained through analysis, where the call relationship information includes: call link, call frequency, call delay, and call error, etc.

[0071] 3) Continuous monitoring

[0072] Establish continuous monitoring mechanisms to ensure that the target system maintains optimal performance under changing load conditions;

[0073] Through this process, the resource consumption information of each business system and the calling relationship information between each business system can be effectively collected and analyzed, thereby providing data support for the optimization and decision-making of the target system.

[0074] Further, the system current limiting method, wherein, in step S200, based on the resource consumption information and the call relationship information, it is determined whether the target system needs to start current limiting;

[0075] In specific implementation, in this embodiment, based on the resource consumption information and the call relationship information, it is determined whether the target system needs to start current limiting, wherein the specific implementation process is as follows:

[0076] 1) Data Collection

[0077] Collect resource consumption information of each business system, including CPU usage, memory usage, QPS, interface processing time, interface error information, etc.

[0078] Collect call relationship information between various business systems, including call links, call frequency, call delay, call errors, etc.;

[0079] 2) Performance baseline setting

[0080] Set a baseline value for each key performance indicator during normal operation. These baseline values ​​are used to compare with the real-time monitoring data (the data collected in step 1 above);

[0081] 3) Real-time monitoring and analysis

[0082] Monitor the performance indicators of each business system in real time and use monitoring tools (such as Prometheus and Grafana) to display real-time data;

[0083] Analyze call link data to understand the flow of requests in the target system;

[0084] 4) Performance indicator evaluation

[0085] Compare real-time monitoring data with preset baseline values ​​to assess whether the target system is operating within the normal range;

[0086] 5) Call relationship evaluation

[0087] Analyze the call frequency and call delay to determine whether there are performance bottlenecks or service response delays;

[0088] Check the call errors and evaluate whether the error rate is within an acceptable range;

[0089] 6) Current limiting start judgment

[0090] Based on the comprehensive evaluation results of performance indicator evaluation and call relationship evaluation, determine whether the target system needs to start current limiting;

[0091] Through this process, we can ensure that when the target system faces the risk of overload, the flow limiting measures are initiated in a timely manner to protect the stability of the target system while minimizing the impact on user experience and business processes.

[0092] Furthermore, in the system flow limiting method, in step S300, when the target system needs to start flow limiting, a flow limiting strategy in the seat dimension is generated according to the output value information of the seat of the target system, including:

[0093] When the target system needs to start current limiting, the output value information of the agent is measured using the random forest algorithm based on the agent portrait, customer portrait and corresponding recommended sales product information of the target system;

[0094] According to the output value information and the preset pressure value that the target system can bear, a corresponding maximum output value is calculated using a dynamic programming algorithm;

[0095] Based on the maximum output value, a flow limiting strategy for the target system seat dimension is generated.

[0096] In specific implementation, in this embodiment, when the target system needs to start flow limiting, a flow limiting strategy of the seat dimension is generated according to the output value information of the seat of the target system, wherein the specific implementation process is as follows:

[0097] 1) Data collection and integration

[0098] Collect data such as agent portraits, customer portraits, and corresponding recommended sales product information of the target system; at the same time, integrate these data to provide input features for the machine learning model;

[0099] 2) Feature selection and processing

[0100] Select features with high correlation with agent output value from the collected data, and perform necessary preprocessing on the features, such as normalization and denoising;

[0101] 3) Seat output value prediction model training

[0102] Use the random forest algorithm to build a seat output value prediction model;

[0103] Train the model through multiple iterations and parameter tuning to improve prediction accuracy;

[0104] 4) Seat output value forecast

[0105] Use the trained random forest model to predict the output value of each seat;

[0106] 5) System load pressure assessment

[0107] Determine the preset bearing pressure value of the target system, which can be obtained based on historical data and system resource capacity;

[0108] 6) Maximum output value calculation

[0109] Using dynamic programming algorithm, combined with seat output value prediction and target system load, the maximum output value under different flow limiting strategies is calculated;

[0110] 7) Current limiting strategy generation

[0111] According to the calculated maximum output value, formulate the flow limiting strategy of the target system seat dimension. The flow limiting strategy may include request release requirements, request rate limit, priority allocation, etc.

[0112] Through this process, we can scientifically formulate and implement flow limiting strategies, which not only ensures the stability of the target system, but also maximizes the output value of seats and achieves the optimal allocation of resources.

[0113] Further, in the system current limiting method, the step S400, based on the current limiting strategy, performs current limiting processing on the target system, includes:

[0114] Sending the current limiting strategy to the gateways of each of the business systems related to the call link in the target system;

[0115] The gateway of each of the business systems releases agent requests that comply with the current limiting strategy to the corresponding business system for processing.

[0116] In the specific implementation, in this embodiment, based on the current limiting strategy, current limiting processing is performed on the target system, wherein the specific implementation process is as follows:

[0117] 1) Development and verification of current limiting strategy

[0118] Ensure that the current limiting strategy has been developed and fully tested to verify its effectiveness and impact on the target system performance;

[0119] 2) Gateway configuration management

[0120] Ensure that the gateways of all business systems support configuration management and can receive and apply new current limiting rules;

[0121] 3) Encapsulation and transmission of current limiting strategies

[0122] Encapsulate the current limiting policies into a configurable format, such as JSON or XML, and ensure that these policies can be transmitted to each gateway in a secure manner;

[0123] 4)Automated configuration updates

[0124] Use automated tools or scripts to update gateway configurations to reduce human error and increase efficiency;

[0125] 5) Gateway policy synchronization

[0126] Ensure that all relevant gateways in the call link can synchronously receive the new current limiting policy and maintain consistency;

[0127] 6) Gateway strategy application

[0128] Apply new flow control policies on the gateway, which can include request release requirements, request rate limits, priority allocation, etc.

[0129] 7) Gateway release mechanism

[0130] Configure the gateway to identify agent requests that meet the current limiting policy and only allow these agent requests to be processed by the corresponding business system;

[0131] 8) Monitoring and logging

[0132] Monitor the performance of the gateway and the status of the released requests, and record relevant logs to facilitate troubleshooting and policy evaluation;

[0133] 9) Exception handling

[0134] Design exception handling processes to quickly respond when the gateway encounters configuration errors or business system failures;

[0135] Through this process, it can be ensured that the flow limiting strategy is effectively implemented, while maintaining the flexibility and responsiveness of the target system to adapt to changing business needs and system loads; moreover, when the flow limiting processing is implemented on the target system according to the flow limiting strategy of the agent dimension, the integrity of the agent business process in the target system can be effectively guaranteed.

[0136] For further information, see Figure 2 , the system current limiting method, wherein, after the step S400, based on the current limiting strategy, the current limiting process is performed on the target system, the step further includes:

[0137] S500: Using a scheduled task, regularly updating the current limiting strategy and sending it to the target system for execution.

[0138] In the specific implementation, in this embodiment, a timed task is used to regularly update the current limiting strategy and send it to the target system for execution (that is, based on the updated current limiting strategy, the target system is subjected to current limiting processing), wherein the specific implementation process is as follows:

[0139] 1) Setting of scheduled tasks

[0140] Use task scheduling tools (such as cron jobs, Windows Task Scheduler, or more advanced workflow scheduling systems) to set up scheduled tasks;

[0141] 2) Strategy evaluation and optimization

[0142] At a predetermined time point, evaluate and optimize the current limiting strategy based on the latest target system performance data and business requirements;

[0143] 3) Strategy update mechanism

[0144] Develop or use existing configuration management tools to update the rate limiting policy, which involves modifying configuration files, database records, or making API calls;

[0145] 4) Automated deployment process

[0146] Ensure that updates to rate limiting policies can be deployed via automated scripts or continuous integration / continuous deployment (CI / CD) processes;

[0147] 5) Version control and tracking

[0148] Use a version control system to manage the change history of the current limiting policy to ensure that the content of each update can be tracked;

[0149] 6) Security and compliance checks

[0150] Before issuing a new rate limiting policy, conduct security and compliance checks to ensure that the new rate limiting policy does not introduce security risks or violate relevant regulations;

[0151] 7) Policy issuance

[0152] Send the updated current limiting policy to the target system in a secure way for execution;

[0153] Through this process, we can ensure that the update of the current limiting strategy is both automated and controllable, while minimizing the impact on the stability of the target system and user services; moreover, the use of scheduled tasks to regularly update and issue current limiting strategies can ensure that when information changes, the output value can be maximized.

[0154] It can be seen from the above method embodiments that the system current limiting method provided by the present invention at least includes: collecting resource consumption information of each business system in the current target system, and analyzing to obtain the call relationship information between each of the business systems; judging whether the target system needs to start current limiting based on the resource consumption information and the call relationship information; when the target system needs to start current limiting, generating a current limiting strategy in the seat dimension according to the output value information of the seat of the target system; implementing current limiting processing on the target system based on the current limiting strategy; and so on. In this way, the method of the present invention can realize current limiting processing on the target system according to the current limiting strategy in the seat dimension, thereby effectively ensuring the integrity of the seat business process in the target system.

[0155] Specifically, the system current limiting method provided by the embodiment of the present invention has at least the following beneficial technical effects on the basis of ensuring the capabilities of the traditional current limiting method:

[0156] 1. The flow control strategy at the agent level is adopted and various business systems related to the business are linked to ensure the integrity of the agent's business. When completing a business, the flow is either limited at the beginning or completed smoothly, thus achieving end-to-end flow control.

[0157] 2. Use the random forest algorithm to combine the agent portrait, customer portrait, and the corresponding recommended sales product information to predict the agent's output value information. Based on the predicted output value and the target system capabilities, a strategy for maximizing output value and limiting traffic can be obtained;

[0158] 3. By using a scheduled update strategy, the target system can ensure that the output value is maximized even when the customer, seat, and recommended product information changes under high pressure.

[0159] It should be understood that, although the present application provides method operation steps as described in the embodiments or flowcharts, more or less operation steps may be included based on conventional or non-creative labor, and these operation steps are not necessarily performed in sequence according to the embodiment or flowchart. The order of steps listed in the embodiment or flowchart is only one way of executing the order of many steps, and does not represent the only execution order. It should be noted that there is not necessarily a certain order between the above steps. A person of ordinary skill in the art can understand from the description of the embodiment of the present invention that in different embodiments, the above steps may have different execution orders, that is, they may be executed in parallel, or they may be executed in exchange, etc. Moreover, at least a part of the steps in the embodiment or flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution order of these sub-steps or stages is not necessarily performed in sequence, but may be executed in turn, alternately or synchronously with other steps or at least a part of the sub-steps or stages of other steps.

[0160] Based on the above method embodiment, please refer to Figure 3 Another embodiment of the present invention further provides a system current limiting device, wherein the device comprises:

[0161] The collection and analysis module 11 is used to collect resource consumption information of each business system in the current target system, and analyze and obtain the call relationship information between each of the business systems;

[0162] A judgment module 12, configured to judge whether the target system needs to start current limiting based on the resource consumption information and the call relationship information;

[0163] A strategy generation module 13 is used to generate a seat-dimensional flow limiting strategy according to the output value information of the seats of the target system when the target system needs to start flow limiting;

[0164] The current limiting module 14 is used to perform current limiting processing on the target system based on the current limiting strategy.

[0165] Furthermore, the system current limiting device collects resource consumption information of each business system in the current target system, and analyzes and obtains the call relationship information between each of the business systems, wherein:

[0166] The resource consumption information includes CPU usage, memory usage, QPS, interface processing time, and interface error information;

[0167] The call relationship information includes call links, call frequencies, call delays, and call errors, etc.

[0168] In the specific implementation, in this embodiment, the resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained by analysis, wherein the specific implementation process is as follows:

[0169] 1) Resource consumption information collection

[0170] Collect resource consumption information of each business system in the current target system, wherein the resource consumption information includes:

[0171] CPU usage: monitor the CPU load to understand whether the processing capacity of each business system has reached a bottleneck;

[0172] Memory usage: Track memory usage to ensure that each business system has sufficient memory resources to process requests;

[0173] QPS (query rate per second): measures the number of requests that each business system can process per second, and is an important indicator for measuring system throughput;

[0174] Interface processing time: Record the processing time of each interface request in each business system to identify performance bottlenecks;

[0175] Interface error information: collects logs and error information of interface call failures in various business systems to facilitate problem diagnosis and repair;

[0176] 2) Call relationship analysis

[0177] Determine the dependencies and calling sequence between the business systems in the target system, and use tracking tools or log analysis to understand the request flow path between the business systems. The call relationship information between the business systems in the current target system can be obtained through analysis, where the call relationship information includes: call link, call frequency, call delay, and call error, etc.

[0178] 3) Continuous monitoring

[0179] Establish continuous monitoring mechanisms to ensure that the target system maintains optimal performance under changing load conditions;

[0180] Through this process, the resource consumption information of each business system and the calling relationship information between each business system can be effectively collected and analyzed, thereby providing data support for the optimization and decision-making of the target system.

[0181] Further, the system current limiting device, wherein, based on the resource consumption information and the call relationship information, it is determined whether the target system needs to start current limiting;

[0182] In specific implementation, in this embodiment, based on the resource consumption information and the call relationship information, it is determined whether the target system needs to start current limiting, wherein the specific implementation process is as follows:

[0183] 1) Data Collection

[0184] Collect resource consumption information of each business system, including CPU usage, memory usage, QPS, interface processing time, interface error information, etc.

[0185] Collect call relationship information between various business systems, including call links, call frequency, call delay, call errors, etc.;

[0186] 2) Performance baseline setting

[0187] Set a baseline value for each key performance indicator during normal operation. These baseline values ​​are used to compare with the real-time monitoring data (the data collected in step 1 above);

[0188] 3) Real-time monitoring and analysis

[0189] Monitor the performance indicators of each business system in real time and use monitoring tools (such as Prometheus and Grafana) to display real-time data;

[0190] Analyze call link data to understand the flow of requests in the target system;

[0191] 4) Performance indicator evaluation

[0192] Compare real-time monitoring data with preset baseline values ​​to assess whether the target system is operating within the normal range;

[0193] 5) Call relationship evaluation

[0194] Analyze the call frequency and call delay to determine whether there are performance bottlenecks or service response delays;

[0195] Check the call errors and evaluate whether the error rate is within an acceptable range;

[0196] 6) Current limiting start judgment

[0197] Based on the comprehensive evaluation results of performance indicator evaluation and call relationship evaluation, determine whether the target system needs to start current limiting;

[0198] Through this process, we can ensure that when the target system faces the risk of overload, the flow limiting measures are initiated in a timely manner to protect the stability of the target system while minimizing the impact on user experience and business processes.

[0199] Furthermore, the system current limiting device, wherein when the target system needs to start current limiting, generates a current limiting strategy in the seat dimension according to the output value information of the seat of the target system, including:

[0200] When the target system needs to start current limiting, the output value information of the agent is measured using the random forest algorithm based on the agent portrait, customer portrait and corresponding recommended sales product information of the target system;

[0201] According to the output value information and the preset pressure value that the target system can bear, a corresponding maximum output value is calculated using a dynamic programming algorithm;

[0202] Based on the maximum output value, a flow limiting strategy for the target system seat dimension is generated.

[0203] In specific implementation, in this embodiment, when the target system needs to start flow limiting, a flow limiting strategy of the seat dimension is generated according to the output value information of the seat of the target system, wherein the specific implementation process is as follows:

[0204] 1) Data collection and integration

[0205] Collect data such as agent portraits, customer portraits, and corresponding recommended sales product information of the target system; at the same time, integrate these data to provide input features for the machine learning model;

[0206] 2) Feature selection and processing

[0207] Select features with high correlation with agent output value from the collected data, and perform necessary preprocessing on the features, such as normalization and denoising;

[0208] 3) Seat output value prediction model training

[0209] Use the random forest algorithm to build a seat output value prediction model;

[0210] Train the model through multiple iterations and parameter tuning to improve prediction accuracy;

[0211] 4) Seat output value forecast

[0212] Use the trained random forest model to predict the output value of each seat;

[0213] 5) System load pressure assessment

[0214] Determine the preset bearing pressure value of the target system, which can be obtained based on historical data and system resource capacity;

[0215] 6) Maximum output value calculation

[0216] Using dynamic programming algorithm, combined with seat output value prediction and target system load, the maximum output value under different flow limiting strategies is calculated;

[0217] 7) Current limiting strategy generation

[0218] According to the calculated maximum output value, formulate the flow limiting strategy of the target system seat dimension. The flow limiting strategy may include request release requirements, request rate limit, priority allocation, etc.

[0219] Through this process, we can scientifically formulate and implement flow limiting strategies, which not only ensures the stability of the target system, but also maximizes the output value of seats and achieves the optimal allocation of resources.

[0220] Furthermore, the system current limiting device, wherein the current limiting process is performed on the target system based on the current limiting strategy, comprises:

[0221] Sending the current limiting strategy to the gateways of each of the business systems related to the call link in the target system;

[0222] The gateway of each of the business systems releases agent requests that comply with the current limiting strategy to the corresponding business system for processing.

[0223] In the specific implementation, in this embodiment, based on the current limiting strategy, current limiting processing is performed on the target system, wherein the specific implementation process is as follows:

[0224] 1) Development and verification of current limiting strategy

[0225] Ensure that the current limiting strategy has been developed and fully tested to verify its effectiveness and impact on the target system performance;

[0226] 2) Gateway configuration management

[0227] Ensure that the gateways of all business systems support configuration management and can receive and apply new current limiting rules;

[0228] 3) Encapsulation and transmission of current limiting strategies

[0229] Encapsulate the current limiting policies into a configurable format, such as JSON or XML, and ensure that these policies can be transmitted to each gateway in a secure manner;

[0230] 4)Automated configuration updates

[0231] Use automated tools or scripts to update gateway configurations to reduce human error and increase efficiency;

[0232] 5) Gateway policy synchronization

[0233] Ensure that all relevant gateways in the call link can synchronously receive the new current limiting policy and maintain consistency;

[0234] 6) Gateway strategy application

[0235] Apply new flow control policies on the gateway, which can include request release requirements, request rate limits, priority allocation, etc.

[0236] 7) Gateway release mechanism

[0237] Configure the gateway to identify agent requests that meet the current limiting policy and only allow these agent requests to be processed by the corresponding business system;

[0238] 8) Monitoring and logging

[0239] Monitor the performance of the gateway and the status of the released requests, and record relevant logs to facilitate troubleshooting and policy evaluation;

[0240] 9) Exception handling

[0241] Design exception handling processes to quickly respond when the gateway encounters configuration errors or business system failures;

[0242] Through this process, it can be ensured that the flow limiting strategy is effectively implemented, while maintaining the flexibility and responsiveness of the target system to adapt to changing business needs and system loads; moreover, when the flow limiting processing is implemented on the target system according to the flow limiting strategy of the agent dimension, the integrity of the agent business process in the target system can be effectively guaranteed.

[0243] For further information, see Figure 4 , the system current limiting device, wherein, further comprises:

[0244] The timing update module 15 is used to adopt a timing task to regularly update the current limiting strategy and send it to the target system for execution.

[0245] In the specific implementation, in this embodiment, a timed task is used to regularly update the current limiting strategy and send it to the target system for execution (that is, based on the updated current limiting strategy, the target system is subjected to current limiting processing), wherein the specific implementation process is as follows:

[0246] 1) Setting of scheduled tasks

[0247] Use task scheduling tools (such as cron jobs, Windows Task Scheduler, or more advanced workflow scheduling systems) to set up scheduled tasks;

[0248] 2) Strategy evaluation and optimization

[0249] At a predetermined time point, evaluate and optimize the current limiting strategy based on the latest target system performance data and business requirements;

[0250] 3) Strategy update mechanism

[0251] Develop or use existing configuration management tools to update the rate limiting policy, which involves modifying configuration files, database records, or making API calls;

[0252] 4) Automated deployment process

[0253] Ensure that updates to rate limiting policies can be deployed via automated scripts or continuous integration / continuous deployment (CI / CD) processes;

[0254] 5) Version control and tracking

[0255] Use a version control system to manage the change history of the current limiting policy to ensure that the content of each update can be tracked;

[0256] 6) Security and compliance checks

[0257] Before issuing a new rate limiting policy, conduct security and compliance checks to ensure that the new rate limiting policy does not introduce security risks or violate relevant regulations;

[0258] 7) Policy issuance

[0259] Send the updated current limiting policy to the target system in a secure way for execution;

[0260] Through this process, we can ensure that the update of the current limiting strategy is both automated and controllable, while minimizing the impact on the stability of the target system and user services; moreover, the use of scheduled tasks to regularly update and issue current limiting strategies can ensure that when information changes, the output value can be maximized.

[0261] It can be seen from the above device embodiments that the system current limiting device provided by the present invention at least includes: collecting resource consumption information of each business system in the current target system, and analyzing to obtain the call relationship information between each of the business systems; judging whether the target system needs to start current limiting based on the resource consumption information and the call relationship information; when the target system needs to start current limiting, generating a current limiting strategy in the seat dimension according to the output value information of the seat of the target system; implementing current limiting processing on the target system based on the current limiting strategy; and so on. In this way, the device of the present invention can implement current limiting processing on the target system according to the current limiting strategy in the seat dimension, thereby effectively ensuring the integrity of the seat business process in the target system.

[0262] Specifically, the system current limiting device provided by the embodiment of the present invention has at least the following beneficial technical effects on the basis of ensuring the capabilities of the traditional current limiting device:

[0263] 1. The flow control strategy at the agent level is adopted and various business systems related to the business are linked to ensure the integrity of the agent's business. When completing a business, the flow is either limited at the beginning or completed smoothly, thus achieving end-to-end flow control.

[0264] 2. Use the random forest algorithm to combine the agent portrait, customer portrait, and the corresponding recommended sales product information to predict the agent's output value information. Based on the predicted output value and the target system capabilities, a strategy for maximizing output value and limiting traffic can be obtained;

[0265] 3. By using a scheduled update strategy, the target system can ensure that the output value is maximized even when the customer, seat, and recommended product information changes under high pressure.

[0266] Based on the above method embodiment, please refer to Figure 5 Another embodiment of the present invention further provides a computer device, wherein the computer device 10 includes:

[0267] memory 120 and one or more processors 110, Figure 5 A processor 110 is used as an example for description. The processor 110 and the memory 120 may be connected via a communication bus or other means. Figure 5 The example of connecting via a communication bus is taken as an example.

[0268] The processor 110 is used to complete various control logics of the computer device 10. It can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a single-chip microcomputer, an ARM (Acorn RISC Machine) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination of these components. In addition, the processor 110 can also be any traditional processor, microprocessor or state machine. The processor 110 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP, or any other such configuration.

[0269] The memory 120 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules, such as the computer program corresponding to the system current limiting method in the embodiment of the present invention. The processor 110 executes various functional applications and data processing of the computer device 10 by running the non-volatile software programs, instructions and units stored in the memory 120, that is, the system current limiting method in the above method embodiment is implemented.

[0270] The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store an application required for operating the device or at least one function; the data storage area may store data created according to the use of the computer device 10, etc. In addition, the memory 120 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 120 may optionally include a memory remotely arranged relative to the processor 110, and these remote memories may be connected to the computer device 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0271] One or more units are stored in the memory 120, and when executed by one or more processors 110, a system current limiting method as in any of the above method embodiments can be implemented, for example, the system current limiting method described above can be implemented. Figure 1 The method comprises steps S100 to S400.

[0272] Those skilled in the art will understand that Figure 5 The hardware structure diagram shown in the figure is only a schematic diagram of a partial structure related to the solution of the present invention, and does not constitute a limitation on the computer device to which the solution of the present invention is applied. The specific computer device may include more components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0273] Based on the above method embodiments, another embodiment of the present invention further provides a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by at least one processor, the system current limiting method in any of the above method embodiments can be implemented, for example, the system current limiting method described above can be implemented. Figure 1 The method comprises steps S100 to S400.

[0274] As an example, the non-volatile storage medium can include a read-only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), an electrically erasable ROM (EEPROM), or a flash memory. Volatile memory can include a random access memory (RAM) as an external cache memory. By way of illustration and not limitation, RAM can be obtained in many forms such as synchronous RAM (SRAM), dynamic RAM, (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synch link DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The disclosed memory components or memories of the operating environment described herein are intended to include one or more of these and / or any other suitable types of memory.

[0275] Based on the above method embodiments, another embodiment of the present invention further provides a computer program product, the computer program product includes a computer program stored on a non-volatile computer-readable storage medium, the computer program includes program instructions, when the program instructions are executed by a processor, the system current limiting method in any of the above method embodiments can be implemented, for example, the above described Figure 1 The method comprises steps S100 to S400.

[0276] The embodiments described above are merely illustrative, in which the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0277] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general hardware platform, and of course can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can exist in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods of each embodiment or some parts of the embodiment.

[0278] Conditional language such as "can," "can," "might," or "may," unless specifically stated otherwise or otherwise understood within the context as used, is generally intended to convey, among other things, that a particular embodiment can include (while other embodiments do not) a particular feature, element, and / or operation. Thus, such conditional language is also generally intended to imply that a feature, element, and / or operation is required for one or more embodiments anyway or that one or more embodiments must include logic for determining, with or without input or prompting, whether such features, elements, and / or operations are included or will be performed in any particular embodiment.

[0279] What has been described herein, in this specification and in the accompanying drawings includes examples that can provide a system current limiting method, device, computer equipment, and non-volatile computer-readable storage medium. Of course, it is not possible to describe every conceivable combination of elements and / or methods for the purpose of describing the various features of the present disclosure, but it can be recognized that many other combinations and permutations of the disclosed features are possible. Therefore, it is obvious that various modifications can be made to the present disclosure without departing from the scope or spirit of the present disclosure, but all these various modifications should belong to the scope of protection of the claims attached to the present invention. In addition, or in an alternative, other embodiments of the present disclosure may be obvious from consideration of the present specification and the accompanying drawings and from the practice of the present disclosure as presented herein. It is intended that the examples proposed in this specification and the accompanying drawings are considered to be illustrative and not restrictive in all respects. Although specific terms are used herein, they are used in a general and descriptive sense and are not used for limiting purposes.

Claims

1. A system current limiting method, characterized in that: include: Collect resource consumption information of each business system in the current target system, and analyze and obtain the call relationship information between each of the business systems; Based on the resource consumption information and the call relationship information, determining whether the target system needs to start current limiting; When the target system needs to start flow limiting, a flow limiting strategy in the seat dimension is generated according to the output value information of the seats of the target system; Based on the current limiting strategy, current limiting processing is performed on the target system.

2. The system current limiting method according to claim 1, characterized in that: When the target system needs to start flow limiting, a flow limiting strategy in the seat dimension is generated according to the output value information of the seats of the target system, including: When the target system needs to start current limiting, the output value information of the agent is measured using the random forest algorithm based on the agent portrait, customer portrait and corresponding recommended sales product information of the target system; According to the output value information and the preset pressure value that the target system can bear, a corresponding maximum output value is calculated using a dynamic programming algorithm; Based on the maximum output value, a flow limiting strategy for the target system seat dimension is generated.

3. The system current limiting method according to claim 2, characterized in that: The implementing current limiting processing on the target system based on the current limiting strategy includes: Sending the current limiting strategy to the gateways of each of the business systems related to the call link in the target system; The gateway of each of the business systems releases agent requests that comply with the current limiting strategy to the corresponding business system for processing.

4. The system current limiting method according to claim 1, 2 or 3, characterized in that: After the current limiting process is performed on the target system based on the current limiting strategy, the method further includes: A scheduled task is used to regularly update the current limiting strategy and send it to the target system for execution.

5. The system current limiting method according to claim 4, characterized in that: The resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained through analysis, wherein: The resource consumption information includes CPU usage, memory usage, QPS, interface processing time, and interface error information.

6. The system current limiting method according to claim 5, characterized in that: The resource consumption information of each business system in the current target system is collected, and the call relationship information between each business system is obtained through analysis, wherein: The call relationship information includes call links, call frequencies, call delays, and call errors.

7. A system current limiting device, characterized in that: include: The collection and analysis module is used to collect resource consumption information of each business system in the current target system, and analyze and obtain the call relationship information between each of the business systems; A judgment module, used for judging whether the target system needs to start current limiting based on the resource consumption information and the call relationship information; A strategy generation module, used for generating a flow limiting strategy in the seat dimension according to the output value information of the seats of the target system when the target system needs to start flow limiting; The current limiting module is used to perform current limiting processing on the target system based on the current limiting strategy.

8. The system current limiting device according to claim 7, characterized in that: Also includes: The timing update module is used to adopt a timing task to regularly update the current limiting strategy and send it to the target system for execution.

9. A computer device, characterized in that: The computer device comprises at least one processor; and, a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor. When the computer program is executed by the at least one processor, the system current limiting method according to any one of claims 1 to 6 can be implemented.

10. A non-volatile computer-readable storage medium, characterized in that: The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by at least one processor, the system current limiting method according to any one of claims 1 to 6 can be implemented.

Images